Use enableAsyncStack instead of addDebuggee in BiDi script module
Categories
(Remote Protocol :: WebDriver BiDi, task)
Tracking
(Not tracked)
People
(Reporter: jdescottes, Unassigned)
References
Details
(Keywords: perf)
In Bug 1770477, we are temporarily using addDebuggee
to enable async stack traces in the script module for WebDriver BiDi, but as soon as Bug 1775207 is fixed, we should switch to the APIs added there (presumably enableAsyncStack
unless naming changes)
Reporter | ||
Comment 1•2 years ago
|
||
This should be about replacing:
this.#global = lazy.dbg.addDebuggee(this.messageHandler.window);
with
this.#global = lazy.dbg.makeGlobalObjectReference(this.messageHandler.window);
lazy.dbg.enableAsyncStack(this.messageHandler.window);
Reporter | ||
Updated•2 years ago
|
Comment 2•2 years ago
|
||
As discussed with Julian this bug is actually not blocking us for M4. Also given that it depends on a platform bug we should not block our M4 on it. We can use P2 and can get it fixed once the dependency has been fixed.
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Given that the dependency bug has been landed earlier as expected I assume that we want to make use of the new feature in M4? Lets discuss today in the triage session.
Reporter | ||
Comment 4•2 years ago
|
||
I would actually propose to fold that in the current stack for Bug 1770477 since it didn't land yet.
Reporter | ||
Comment 5•2 years ago
|
||
Let's handle it in Bug 1770477
Updated•2 years ago
|
Description
•