Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 12501] GLib-ERROR**:gmem.c:110:failed to allocate 8388608

Date: Thu, 09 Jun 2016 03:08:03 +0000

Comment # 12 on bug 12501 from
(In reply to Prajith Veetil from comment #7)
> Attached is task manager's view when wireshark crashes. It is using upto 3GB
> of memory.

Is that what "36,90,000K" means?  I've never seen such notation...  Weird.

3 Gbytes is about the max for a 32-bit Windows application (if Windows is
configured to allow processes to have more than 2 Gbytes of memory)--so that
sort-of explains the crash.

But I can load this capture file very quickly (load time: 3.5 seconds) and my
Wireshark takes less than half a Gbyte of memory.  Admittedly this is on Linux
and 64-bit.  But still...

Do you have any custom plugins or Lua dissectors running?

Or maybe it's your preferences?  (Could you attach your preferences file? The
location is specified in one of the tabs of the Help->About dialog).


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