• News
  • Get Acquainted ▼
    • About
    • Download
    • Blog
  • Get Help ▼
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Issue Tracker
  • Develop ▼
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds
  • Project Host
  • SharkFest
Wireshark-bugs: [Wireshark-bugs] [Bug 10068] tshark, running on MacOS 10.9, performing the stat
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 06 May 2014 02:22:31 +0000

Comment # 5 on bug 10068 from Guy Harris
So what is the memory usage you get from tshark if you run that statistic on
Mountain Lion and on Mavericks (same statistic, tshark rather than Wireshark on
both machines, same capture file)?


You are receiving this mail because:
  • You are watching all bug changes.
  • References:
    • [Wireshark-bugs] [Bug 10068] New: tshark, running on MacOS 10.9, performing the stat function, uses all memory and triggers Out Of Application Memory Errors
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 10068] tshark, running on MacOS 10.9, performing the stat function, uses all memory and triggers Out Of Application Memory Errors
  • Next by Date: [Wireshark-bugs] [Bug 10077] New: Buildbot crash output: randpkt-2014-05-06-26386.pcap
  • Previous by thread: [Wireshark-bugs] [Bug 10068] tshark, running on MacOS 10.9, performing the stat function, uses all memory and triggers Out Of Application Memory Errors
  • Next by thread: [Wireshark-bugs] [Bug 10068] tshark, running on MacOS 10.9, performing the stat function, uses all memory and triggers Out Of Application Memory Errors
  • Index(es):
    • Date
    • Thread
Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation Back to top