https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2287
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeff.morriss.ws@xxxxxxxxx
Status|NEW |RESOLVED
Resolution| |WONTFIX
--- Comment #2 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2008-07-07 10:09:33 PDT ---
The "glib failed to allocate..." error is just another error that comes as a
result of being out of memory.
As for the (new) non-linear memory growth, it may have to do with something new
that Wireshark is doing (e.g., keeping track of more things than it used to).
BTW there is no picture attached to this bug.
As Jaap mentioned the preferred way to capture for a long time is using the
'dumpcap' utility. It does not have the memory usage issue of the
full-dissection tools.
Our memory usage is not something we really aim to do anything about (meaning:
Wireshark's task is generally to dissect as much as possible but it is not
designed to be a let-it-run-all-the-time network monitor), I'm closing this
one.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.