Closed
Bug 1211552
Opened 11 years ago
Closed 3 years ago
Intermittent test_setlinedash.html | application timed out after 330 seconds with no output
Categories
(Core :: Graphics: Canvas2D, defect, P3)
Core
Graphics: Canvas2D
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: KWierso, Unassigned)
Details
(Keywords: intermittent-failure, Whiteboard: [gfx-noted])
Updated•10 years ago
|
Whiteboard: [gfx-noted]
Comment 1•10 years ago
|
||
I hit this same crash on a bc2 run on a try push:
https://treeherder.mozilla.org/logviewer.html#?job_id=15188675&repo=try
The stack is basically entirely in system libraries, and the screenshot is all black with a mouse cursor:
http://mozilla-releng-blobs.s3.amazonaws.com/blobs/try/sha512/7d3e92ad7fed34d21efa55eb526211406cad8133905b12c225a5b07f77ae4b86ee57e6ddc873d8d6d0686b601619ece6438cddceecbbdff2661518bdad25a70c
I think this indicates a machine problem or a driver crash or something.
Comment 2•10 years ago
|
||
If you file hangs with the nearly-always-useless "crash" (that we provoked after the hang) instead of the fact that they were hangs, you'll attract a bad crowd like that, claiming that their startup hang after a bad reboot or whatever it was is your test-specific hang.
Summary: Intermittent test_setlinedash.html | application crashed [@ mach_msg_trap + 0xa] → Intermittent test_setlinedash.html | application timed out after 330 seconds with no output
Comment 3•10 years ago
|
||
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Updated•3 years ago
|
Severity: normal → S3
Comment 4•3 years ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit auto_nag documentation.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•