Open Bug 1776962 Opened 9 months ago Updated 6 days ago

Intermittent dom/workers/test/test_sharedworker_event_listener_leaks.html | single tracking bug


(Core :: DOM: Workers, defect, P3)




Tracking Status
firefox-esr91 --- unaffected
firefox-esr102 --- unaffected
firefox102 --- unaffected
firefox103 --- unaffected
firefox104 --- affected


(Reporter: jmaher, Assigned: asuth)




(Keywords: intermittent-failure, intermittent-testcase, regression, Whiteboard: [retriggered])

No description provided.

Additional information about this bug failures and frequency patterns can be found by running: ./mach test-info failure-report --bug 1776962

(In reply to Natalia Csoregi [:nataliaCs] from comment #2)

First occurrence:

Luca, can you take a look please?

Sure thing,
The patch landed from Bug 1685627 should be basically a no-op for webcontent workers and only affect workers created from a moz-extension url worker script.

But I'll dig a bit more to see if I can get some more details useful to confirm that it is the regressing change (or that would exclude it with absolute certainty), I don't exclude that I may be not seeing the correlation between the two just yet.

I think the regression finding may have stopped a little early on the test jobs as it doesn't look like the patch could have introduced the problem[1], but after looking at this with :rpl I think at least one obvious thing we can do to improve things here is to automatically close the SharedWorker binding on DOMEventTargetHelper::DisconnectFromOwner which will drop the mWindow strong ref which is cycle-collected but doesn't need to wait that long.

1: That is, I Think if tests had been run on older jobs than we would find that the test failures continued to happen.

Assignee: nobody → bugmail
Flags: needinfo?(lgreco)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.