https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3948
--- Comment #2 from didier gautheron <dgautheron@xxxxxxxx> 2009-08-26 11:43:51 PDT ---
(In reply to comment #1)
> Committed revision 29566.
>
> It looks like there may be more memory leaks
> Used mem with trace loaded 68900, with expert info 81608 after
> destroying window 77912.
>
Possible but running valgrind is slow... On the other hand here:
after loading 257M, after expert info composite 325M but after re opening
expert info composite a couple of time the memory is still at 325M.
It could glib allocator not returning freed memory to the OS.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.