Wireshark-bugs: [Wireshark-bugs] [Bug 13226] Buildbot crash output: fuzz-2016-12-08-5712.pcap

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 10 Dec 2016 03:27:00 +0000

Comment # 5 on bug 13226 from 
The CPU time limit seems to be set to 300 seconds.  On my MacBook Pro, "tshark
-n -V" on that capture file takes about 12 CPU seconds; I don't know how much
Valgrind slows the processing down, but if it's more than a factor of 25 or so,
that could push the CPU time over 300 seconds.

The Valgrind manual:

    http://valgrind.org/docs/manual/manual-core.html

says

    At one end of the scale, Memcheck adds code to check every memory access
and every value computed, making it run 10-50 times slower than natively.

so it could conceivably push TShark over the edge for that file.

Shall we try boosting the max CPU time to 600 seconds?

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