`devtools/client/debugger/test/mochitest/examples/sourcemaps-with-sections/xbundle.js` is, in full, a `setInterval` that throws every second with nothing clearing it. Ten tests load the fixture page that pulls it in, and only `browser_dbg-breakpoints-sourcemap-with-sections.js` wants the timer. The other nine take a thrown error every second while their tab is open. That error defeats the harness timeout. `browser-test.js` extends a test by up to ten further windows as long as console output stays fresh, and every console-service message stamps `lastOutputTime`. A 1 Hz uncaught error keeps that freshness check passing forever, so a hung test burns every extension instead of failing after one. The fix is to move `xbundle.js` to its own fixture page and point the one test that needs it there. The other nine want a try push first, since they lose extensions they get for free today.
Bug 2070933 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
`devtools/client/debugger/test/mochitest/examples/sourcemaps-with-sections/xbundle.js` is, in full, a `setInterval` that throws every second with nothing clearing it. Ten tests load the fixture page that pulls it in, and only `browser_dbg-breakpoints-sourcemap-with-sections.js` wants the timer. The other nine take a thrown error every second while their tab is open. That error defeats the harness timeout. `browser-test.js` extends a test by up to ten further windows as long as console output stays fresh, and every console-service message stamps `lastOutputTime`. A 1 Hz uncaught error keeps that freshness check passing forever, so a hung test burns every extension instead of failing after one. The fix is to move `xbundle.js` to its own fixture page and point the one test that needs it there.