Open Bug 1620023 Opened 5 years ago Updated 3 years ago

Investigate why the debugger / worker targets fails against subprocess workers

Categories

(DevTools :: Debugger, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: ochameau, Unassigned)

References

Details

Firefox codebase uses workers for "subprocess":
https://searchfox.org/mozilla-central/search?q=&case=false&regexp=false&path=subprocess%2F
Thes workers appear to prevent the browser toolbox from opening.
It looks like the Worker Target are not able to fully initialize.
The following error appears:

JavaScript error: resource://devtools/server/startup/worker.js, line 37: NetworkError: WorkerDebuggerGlobalScope.loadSubScript: Failed to load worker script at resource://devtools/shared/worker/loader.js (nsresult = 0x805e0006)

A workaround code is being landed in bug 1594754 which comes from here:
https://searchfox.org/mozilla-central/rev/c79c0d65a183d9d38676855f455a5c6a7f7dadd3/devtools/client/debugger/src/client/firefox/targets.js#80-82

It would be great to stop blacklisting these workers and figure out why we can't debug them.

The priority flag is not set for this bug.
:jlast, could you have a look please?

For more information, please visit auto_nag documentation.

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