Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] Wireshark Memory alloc question

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Jaap Keuter <jaap.keuter@xxxxxxxxx>
Date: Fri, 04 Apr 2008 13:18:19 +0200

Hi,

Yes, good idea. Can you tell us *when* we can free memory?

Thanx,
Jaap

rmkml wrote:
Hi,
On README.malloc file, wireshark have two functions:
-Ephemeral allocations: This functions allocate memory that will be automatically freed once the current packet dissection completes.
-Seasonal allocations: This functions allocate memory that will stay around a lot longer but will be automatically freed once the current capture is closed and Wireshark opens a new capture.

Very good, this two functions work very well on open/close pcap file,
but when wireshark/tshark run on live trafic (pcap_open_live), *shark more alloc without freeing.

Maybe it is possible add new function or modify *shark code for malloc freeing on live analysis ?

Regards
Rmkml
Crusoe-Researches.com



  • Follow-Ups:
    • Re: [Wireshark-dev] Wireshark Memory alloc question
      • From: rmkml
  • References:
    • [Wireshark-dev] Wireshark Memory alloc question
      • From: rmkml
  • Prev by Date: Re: [Wireshark-dev] [Wireshark-commits] rev 24766: /trunk/epan/ /trunk/epan/: libwireshark.def
  • Next by Date: Re: [Wireshark-dev] Wireshark Memory alloc question
  • Previous by thread: [Wireshark-dev] Wireshark Memory alloc question
  • Next by thread: Re: [Wireshark-dev] Wireshark Memory alloc question
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation