Closed Bug 610062 Opened 15 years ago Closed 13 years ago

TEST-UNEXPECTED-FAIL | /tests/modules/plugin/test/test_streamNotify.html | application timed out after 330 seconds with no output, followed by PROCESS-CRASH

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: Margaret, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1288993694.1288997472.19145.gz&fulltext=1 s: talos-r3-snow-052 TEST-UNEXPECTED-FAIL | /tests/modules/plugin/test/test_streamNotify.html | application timed out after 330 seconds with no output PROCESS-CRASH | /tests/modules/plugin/test/test_streamNotify.html | application crashed (minidump found) Thread 0 (crashed) PROCESS-CRASH | /tests/modules/plugin/test/test_streamNotify.html | application crashed (minidump found) Thread 0 (crashed) PROCESS-CRASH | /tests/modules/plugin/test/test_streamNotify.html | application crashed (minidump found) Thread 0 (crashed) TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | missing output line for total leaks! TEST-UNEXPECTED-FAIL | plugin process 376 | automationutils.processLeakLog() | leaked 112 bytes during test execution TEST-UNEXPECTED-FAIL | plugin process 376 | automationutils.processLeakLog() | leaked 2 instances of ChildNPObject with size 32 bytes each (64 bytes total) TEST-UNEXPECTED-FAIL | plugin process 376 | automationutils.processLeakLog() | leaked 3 instances of NPObject with size 16 bytes each (48 bytes total)
Blocks: 438871
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]
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.