https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4051
--- Comment #6 from Gerfl <gkrames@xxxxxxx> 2009-10-24 09:33:01 PDT ---
Hi folks,
it got a bit silent about this bug, which I consider a severe endurance
problem.
Note that IMHO the title is misleading. The actual issue is: TCPdissector
leaks memory with every tcp packet and connection; the title is about a
cosmetic consequential problem.
I have retested with "tcp.analyze_sequence_numbers: FALSE", with the
consequence that it takes about 3 times as long as before the out-of-memory
error occurs, but still it occurs.
For demonstrating the bug, run "tshark -c .... -i yourIf ..." with valgrind and
some trivial TCP traffic (generated by netcat) and all upper-level dissectors
turned off.
Unfortunately I lack the in-depth knowledge of the wireshark source-level
design to decide where the leak actually happens and how it is best prevented.
If a knowledgeful person would take a look at this one, I would highly
appreciate.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.