Memory leak

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Memory leak

Dimitar DIMITROV-12
1. valgrind --leak-check=full --show-reachable=yes ./vim -u NONE -U NONE

2. ZQ

==14191== LEAK SUMMARY:
==14191==    definitely lost: 36 bytes in 1 blocks.
==14191==    indirectly lost: 120 bytes in 10 blocks.
==14191==      possibly lost: 0 bytes in 0 blocks.
==14191==    still reachable: 40,689 bytes in 261 blocks.
==14191==         suppressed: 0 bytes in 0 blocks.

VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Jul 13 2010 20:27:14)
Included patches: 1-446
Compiled by mitko@debian
Normal version without GUI.  Features included (+) or not (-):
-arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset +cindent -clientserver -clipboard +cmdline_compl
+cmdline_hist +cmdline_info +comments +cryptv -cscope +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic
-emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path +find_in_path +float +folding -footer +fork()
-gettext -hangul_input -iconv +insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent +listcmds
+localmap +menu +mksession +modify_fname +mouse -mouseshape -mouse_dec -mouse_gpm -mouse_jsbterm -mouse_netterm
-mouse_sysmouse +mouse_xterm -multi_byte +multi_lang -mzscheme -netbeans_intg -osfiletype +path_extra -perl
+postscript +printer -profile -python +quickfix +reltime -rightleft -ruby +scrollbind -signs +smartindent -sniff
+startuptime +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl +terminfo
+termresponse +textobjects +title -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
+vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_save
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -O2 -fno-strength-reduce -Wall -D_FORTIFY_SOURCE=1
Linking: gcc   -L/usr/local/lib -o vim       -lm -lncurses

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Memory leak

Bram Moolenaar

Dimitar wrote:

> 1. valgrind --leak-check=full --show-reachable=yes ./vim -u NONE -U NONE
>
> 2. ZQ
>
> ==14191== LEAK SUMMARY:
> ==14191==    definitely lost: 36 bytes in 1 blocks.
> ==14191==    indirectly lost: 120 bytes in 10 blocks.
> ==14191==      possibly lost: 0 bytes in 0 blocks.
> ==14191==    still reachable: 40,689 bytes in 261 blocks.
> ==14191==         suppressed: 0 bytes in 0 blocks.
>
> VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Jul 13 2010 20:27:14)
> Included patches: 1-446
[...]

Please check where the leaks are.  At least some of them will be in
libraries.  Those can't be avoided.  And you need to compile Vim with
EXITFREE defined, otherwise it won't clean up.

--
A real patriot is the fellow who gets a parking ticket and rejoices
that the system works.


 /// Bram Moolenaar -- [hidden email] -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Loading...