Closed Bug 635066 Opened 14 years ago Closed 12 years ago

Intermittent test suite timeout in modules/plugin/test/test_npruntime_npninvoke.html | application timed out after 330 seconds with no output

Categories

(Core Graveyard :: Plug-ins, defect)

x86_64
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ehsan.akhgari, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1297978691.1297982207.31937.gz Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central debug test mochitest-other on 2011/02/17 13:38:11 397 INFO TEST-START | /tests/modules/plugin/test/test_npruntime_npninvoke.html --DOMWINDOW == 22 (0x11e9cdb98) [serial = 71] [outer = 0x122d7cfa0] [url = http://mochi.test:8888/tests/modules/plugin/test/test_npruntime_identifiers.html] --DOMWINDOW == 21 (0x1218566f8) [serial = 70] [outer = 0x122d7cfa0] [url = http://mochi.test:8888/tests/modules/plugin/test/test_npruntime_construct.html] --DOMWINDOW == 20 (0x11e97d5f8) [serial = 62] [outer = 0x122d7cfa0] [url = http://mochi.test:8888/tests/modules/plugin/test/test_instantiation.html] --DOMWINDOW == 19 (0x11e579238) [serial = 69] [outer = 0x122d7cfa0] [url = http://mochi.test:8888/tests/modules/plugin/test/test_npobject_getters.html] --DOMWINDOW == 18 (0x11e981118) [serial = 67] [outer = 0x122d7cfa0] [url = http://mochi.test:8888/tests/modules/plugin/test/test_npn_asynccall.html] ++DOMWINDOW == 19 (0x11e5bdbc8) [serial = 73] [outer = 0x122d7cfa0] NEXT ERROR TEST-UNEXPECTED-FAIL | /tests/modules/plugin/test/test_npruntime_npninvoke.html | application timed out after 330 seconds with no output Can't trigger Breakpad, just killing process INFO | automation.py | Application ran for: 0:06:25.814636 INFO | automation.py | Reading PID log: /var/folders/H5/H5TD8hgwEqKq9hgKlayjWU+++TM/-Tmp-/tmpJIb_gPpidlog NEXT ERROR PROCESS-CRASH | /tests/modules/plugin/test/test_npruntime_npninvoke.html | application crashed (minidump found) Operating system: Mac OS X 10.6.6 10J567 CPU: amd64 family 6 model 23 stepping 10 2 CPUs Crash reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS Crash address: 0x0 NEXT ERROR Thread 0 (crashed) 0 libnptest.dylib!Crash [nptest.cpp:8812253737ce : 85 + 0x4] rbx = 0x039b30b6 r12 = 0x5fbfb580 r13 = 0x00000000 r14 = 0x03815c40 r15 = 0x03815c40 rip = 0x039b247c rsp = 0x5fbfb450 rbp = 0x5fbfb450 Found by: given as instruction pointer in context 1 libnptest.dylib!IntentionalCrash [nptest.cpp:8812253737ce : 93 + 0x4] rbx = 0x039b30b6 r12 = 0x5fbfb580 r13 = 0x00000000 r14 = 0x03815c40 r15 = 0x03815c40 rip = 0x039b4e7f rsp = 0x5fbfb460 rbp = 0x5fbfb460 Found by: call frame info
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that: * Haven't changed in > 6months * Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb} * Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive. I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases). Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
(OrangeWFM bugs not touched for 2 months)
Status: REOPENED → RESOLVED
Closed: 13 years ago12 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.