Closed Bug 1290856 Opened 4 years ago Closed 2 years ago

Intermittent TEST-UNEXPECTED-TIMEOUT | dom/media/tests/mochitest/test_peerConnection_localRollback.html | application timed out after 330 seconds with no output

Categories

(Core :: JavaScript: GC, defect, P3)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Assigned: bwc)

References

(Depends on 1 open bug)

Details

(Keywords: bulk-close-intermittents, intermittent-failure)

Looks like a deadlock or something in the garbage collector.
Component: WebRTC → XPCOM
Component: XPCOM → JavaScript: GC
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
We seem to be crashing in NrUdpSocketIpc::create. Seems to have started pretty recently, looking into it.
Ok, I'm pretty sure this is the same failure as bug 1298290. It is likely that bug 1411977 changed the logging output enough that it looked like a new intermittent.
See Also: → 1298290
It looks like the io_thread_ is null in NrSocketUdpIpc::create somehow. Digging deeper.
Depends on: 1442404
The only timeout in this test since bug 1442404 landed was a case of bug 1443468.
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
Status: REOPENED → RESOLVED
Closed: 3 years ago2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.