STRs:

• run ./mach test browser_spectrum.js --jsdebugger
• wait for 15s
• (note: this is all done without starting the test, ie without focusing the chrome window which will trigger the test)

ER: should be fine
AR: the browser toolbox UI is split in 2, with the left half showing the usual "toolbox timeout" message.

After that, if you had a debugger statement in the test script, and you start the test, the debugger will visibly break (green toolbox toolbar icon), but you won't see the script, the scope etc...

I tend to have the issue regularly when I'm trying to open files in the debugger before running the test, because it will usually give enough time for some connection to timeout

I see the following error in the logs:

JavaScript error: resource://devtools/shared/resources/legacy-target-watchers/legacy-workers-watcher.js, line 46: TypeError: can't access property Symbol.iterator, existingTargets is undefined

Fixing this doesn't help.

Another one:

Error when attaching target: Error: Connection closed, pending request to server1.conn0.contentProcess41778/thread3, type isAttached failed

Request stack:
request@resource://devtools/shared/protocol/Front.js:285:14
generateRequestMethods/</frontProto[name]@resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:46:19
attachThread@resource://devtools/client/fronts/targets/target-mixin.js:543:33

Looks like the corresponding thread actor was already destroyed?

Nicolas, did you have different STRs?

Note that this seems intermittent, I get it a little more than 50% of the time locally.

(In reply to Julian Descottes [:jdescottes] from comment #3)

Nicolas, did you have different STRs?

My use case was adding a debugger statement in the test and running it with jsdebugger , but I can't reproduce today of course