Wireshark-bugs: [Wireshark-bugs] [Bug 4115] Wireshark crashes while opening large trace files on
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4115
Mark R Lindsey <mark@xxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark@xxxxxxxxxxxx
--- Comment #10 from Mark R Lindsey <mark@xxxxxxxxxxxx> 2010-04-20 20:15:59 PDT ---
I'm still having this problem with 1.3.4 (svn rev 32340) and with version
1.2.7.
I'm trying to open a 900 MB pcap. My machine has 8 GB of RAM.
Attempt 1: Crashed at
Resident Size: 1616088 kbytes
VM Size: 3384016 kbytes
Attempt 2: Crashed at:
Resident Size: 1489512 kbytes
VM Size: 3376848 kbytes
Attempt 2 Details from Activity Monitor as of the point of crash:
Real Memory Size: 1.42 GB
Virtual Memory Size: 3.72 GB
Shared Memory Size: 2.9 MB
Private Memory Size: 1.41 GB
Virtual Private Memory: 3.10 GB
In both cases, the progress meter reported that it had loaded somewhere over
60% (i.e., >500 MB).
Apr 20 22:10:46 nabla wireshark-bin[4519]: wireshark-bin(4519,0xa06b94e0)
malloc: *** mmap(size=16777216) failed (error code=12)\n**
* error: can't allocate region\n*** set a breakpoint in malloc_error_break to
debug
Apr 20 22:10:46 nabla [0x0-0xc90c9].org.wireshark.Wireshark[4416]:
wireshark-bin(4519,0xa06b94e0) malloc: *** mmap(size=16777216) fa
iled (error code=12)
Apr 20 22:10:46 nabla [0x0-0xc90c9].org.wireshark.Wireshark[4416]: *** error:
can't allocate region
Apr 20 22:10:46 nabla [0x0-0xc90c9].org.wireshark.Wireshark[4416]: *** set a
breakpoint in malloc_error_break to debug
Apr 20 22:10:46 nabla [0x0-0xc90c9].org.wireshark.Wireshark[4416]:
***MEMORY-ERROR***: wireshark-bin[4519]: GSlice: failed to alloca
te 4088 bytes (alignment: 4096): Cannot allocate memory
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
