So I [triggered a pernosco session](https://pernos.co/debug/hFEdsJyuJlfrq1MPR9o-PA/index.html) and the failure reproduces also there. I see that apparently `StaticPrefs::dom_abort_script_on_child_shutdown` is set in that run, and in that task log I see an execution of our test. I assume the pref just remains set after test runs, which is not what we wanted. I [see no possibility to define prefs inside the mochitest.ini](https://firefox-source-docs.mozilla.org/build/buildsystem/test_manifests.html) but we have this for crashtests. So we probably want to transform that test into a crashtest.
Bug 1777198 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
~~So I [triggered a pernosco session](https://pernos.co/debug/hFEdsJyuJlfrq1MPR9o-PA/index.html) and the failure reproduces also there. I see that apparently `StaticPrefs::dom_abort_script_on_child_shutdown` is set in that run, and in that task log I see an execution of our test.~~ ~~I assume the pref just remains set after test runs, which is not what we wanted. I [see no possibility to define prefs inside the mochitest.ini](https://firefox-source-docs.mozilla.org/build/buildsystem/test_manifests.html) but we have this for crashtests. So we probably want to transform that test into a crashtest.~~ Scratch that, not sure what I was looking at the other week, but AFAICS my test is just leaking.