I have a question...

In the current implementation, each WorkerThread has its own InspectorTaskRunner. This architecture enables to run debugger tasks only for a specific WorkletGlobalScope during pause on the global scope (see WorkerThread::startRunningDebuggerTasksOnPauseOnWorkerThread). After this cleanup, one InspectorTaskRunner manages all debugger tasks for all WorkerThreads on one WorkerBackingThread. This means the debugger is no longer able to run tasks only for a specific WorkletGlobalScope on pause. Is this right behavior?

I think this is right behavior, since worklets share the thread and so pausing one of them should prevent others from doing anything. This would be a natural expectation for the user debugging tasks on a single thread.

Thank you for the clarification. I'll write a design document.

Any progress (or plans) on this?

No progress/plan for now...

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

(Worker bug triage)

nhiroki@: Any updates?

No updates. We've been drastically changing worker startup and worker inspector setup sequence (e.g., issue 835717, issue 882467), so it may be better to consider this after that.