http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1419
ulf.lamping@xxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|memory accumulates after |dumpcap keeps running after
|restart and dumpcap* |Wireshark crashes
------- Comment #1 from ulf.lamping@xxxxxx 2007-03-10 11:05 GMT -------
Well, first of all, putting two bugs into one bug report is a very bad idea and
makes individual traces of the two bugs hard to get - especially when the
report get's older.
1) There may be memory leaks, but a bug report at this level won't help a lot.
In addition, WS won't release all memory for speedup reasons. And in addition
to this, the Windows mechanisms to get the memory consumption of an application
(task manager) is simply lying - don't really trust it!
Unless someone takes a much deeper look into this, I'll take this one as
WONTFIX.
2) Yes, this is a bug which should be fixed. If Wireshark is running out of
memory it should (at least try to) close dumpcap - which it currently does not.
I've changed the summary accordingly.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.