Closed Bug 1262951 Opened 9 years ago Closed 7 years ago

Intermittent 784600.html | application timed out after 330 seconds with no output

Categories

(Core :: Graphics: WebRender, defect, P3)

55 Branch
x86_64
Linux
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox54 --- unaffected
firefox55 --- fixed

People

(Reporter: philor, Assigned: kats)

References

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell fixed:product])

Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Summary: Intermittent 784600.html | application timed out after 330 seconds with no output misreported as | application crashed [@ CrashingThread(void *)] → Intermittent 784600.html | application timed out after 330 seconds with no output
Although there were some earlier failures, this bug was essentially dormant before May 2. Since then, nearly all failures are linux64-qr, debug. :kats -- I notice some of the earliest linux64-qr reports are from your try pushes. Do you know what's going on here?
Flags: needinfo?(bugmail)
Whiteboard: [stockwell needswork]
This is probably specific to webrender then. Not sure offhand what the problem is but I'll see if I can find time to investigate.
Component: Layout → Graphics: WebRender
Flags: needinfo?(bugmail)
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Version: Trunk → 55 Branch
Bug 1365196 seems like it resolves a lot of timeout-related test failures we've been seeing on linux64-qr test jobs. So it might help here as well. I'll keep an eye on this after that lands to see if the frequency goes down.
Bug 1365196 seems to have helped here, and it got merged to central as well on Friday. Will keep this open for a few more days and check that the OF for this bug remains at zero.
Assignee: nobody → bugmail
Depends on: 1365196
Yup, calling this fixed by bug 1365196.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Whiteboard: [stockwell needswork] → [stockwell fixed:product]
You need to log in before you can comment on or make changes to this bug.