Wireshark-bugs: [Wireshark-bugs] [Bug 8064] New: Two Buildbot crash dumps (not previously entere
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 05 Dec 2012 20:51:54 +0000
Bug ID 8064
Summary Two Buildbot crash dumps (not previously entered as bugs).
Classification Unclassified
Product Wireshark
Version SVN
Hardware x86
OS Ubuntu
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter wmeier@newsguy.com 

Build Information:
Dev SVN
--
(At least) two Buildbot fuzz crashes didn't get reported recently (presumably
due to issues (now fixed) related to the recent Bugzilla upgrade).

The details:

http://buildbot.wireshark.org/trunk/builders/Clang-Code-Analysis/builds/1637
https://www.wireshark.org/download/automated/captures/fuzz-2012-12-04-17119.pcap

http://buildbot.wireshark.org/trunk/builders/Clang-Code-Analysis/builds/1638
https://www.wireshark.org/download/automated/captures/fuzz-2012-12-04-24952.pcap

The input file in each case: 9614-ipv4.pcap

Given the input file I expect these crashes are related to Bug #8043 so I'm
going to mark this bug as a dup of Bug #8043.

------------------
[Build 1638]

    /home/wireshark/menagerie/menagerie/9614-ipv4.pcap: (-nVxr) 
 ERROR
Processing failed. Capture info follows:

  Input file: /home/wireshark/menagerie/menagerie/9614-ipv4.pcap
stderr follows:

Command and args:
/home/wireshark/builders/trunk-clang-ca/clangcodeanalysis/install/bin/tshark
-nVxr

** (process:7112): WARNING **: Too many taps queued

** (process:7112): WARNING **: Too many taps queued

<snip many repeated>

** (process:7112): WARNING **: Too many taps queued
Out Of Memory!

Sorry, but TShark has to terminate now!

Some infos / workarounds can be found at:
http://wiki.wireshark.org/KnownBugs/OutOfMemory
**
ERROR:wmem_scopes.c:128:wmem_leave_file_scope: assertion failed:
(!in_packet_scope)

------------------

[Build 1637]

The out was similar to the above except that the last line was:

***MEMORY-ERROR***: [31700]: GSlice: failed to allocate 496 bytes (alignment:
512): Cannot allocate memory

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