Wireshark-bugs: [Wireshark-bugs] [Bug 12501] GLib-ERROR**:gmem.c:110:failed to allocate 8388608
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 08 Jun 2016 20:04:28 +0000

Comment # 3 on bug 12501 from 
That message means Wireshark is running out of memory.  It's trying to allocate
8 Gbytes of memory for something.  That's a fair amount but not so much that
it's obviously a bug.

Does this happen with larger capture files?  If not then could you attach one
of those files to the bug?  (We could, if necessary, mark it private so only
Wireshark's core developers have access.)

It appears you have lots of RAM available but you're running the 32-bit version
of Wireshark.  Any reason you're not running the 64-bit version?  The 64-bit
version will let Wireshark use more memory which will be very beneficial if
you're looking at bigger capture files.

For completeness see:

https://wiki.wireshark.org/KnownBugs/OutOfMemory

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