Wireshark-bugs: [Wireshark-bugs] [Bug 8093] frame_proto_data freed between frames
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 02 Mar 2013 18:20:05 +0000

Comment # 4 on bug 8093 from 
(In reply to comment #3)
> I believe Guy is correct.
> 
> What do you mean that frame_data_cleanup does not free the memory? Which
> memory is it not freeing?

He's probably referring to the per-packet data attached to pfd in the
frame_data structure.

Dissectors are probably either using se_ allocated memory, so they get freed
when the capture is closed (in the case of tshark, that would happen when it
exits), or are keeping track of it themselves, and have an init routine
registered that frees up any old data.

Ideally, there should be another memory pool for per-packet data, which would
be released after each packet in one-pass tshark and released after a file is
closed in Wireshark and two-pass tshark, to reduce the ongoing memory
consumption by one-pass tshark.

You are receiving this mail because:
  • You are watching all bug changes.