Closed
Bug 1601504
Opened 5 years ago
Closed 5 years ago
Console's async stack traces don't work without `javascript.options.asyncstack` enabled
Categories
(DevTools :: Console, defect, P2)
DevTools
Console
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1601179
People
(Reporter: Harald, Unassigned)
References
(Blocks 2 open bugs)
Details
What were you doing?
- Disable
javascript.options.asyncstack
(Nightly only) - Open Console
- Open https://firefox-devtools-async-console-trace.glitch.me/
- Click one of the buttons, like
kitchensink
What happened?
No async stack traces.
What should have happened?
Async stacks traces work.
I assumed javascript.options.asyncstack
is only needed to get async stacks even when DevTools isn't opened.
I also noticed that javascript.options.asyncstack
is off on DevEdition, even though past documentation (and mentions in bug 1200832) I remember says that its enabled.
Reporter | ||
Comment 1•5 years ago
|
||
Jim, can you confirm if this expected and that I didn't misunderstand your explainer of what javascript.options.asyncstack
does?
I guess bug 1342047 should have enabled the behavior as far as I understood it. And bug 1589523 is a new idea to make the pref redundant.
Flags: needinfo?(jimb)
Reporter | ||
Updated•5 years ago
|
Depends on: 1592969
Summary: Console's async stack traces don't without `javascript.options.asyncstack` enabled → Console's async stack traces don't work without `javascript.options.asyncstack` enabled
Reporter | ||
Updated•5 years ago
|
Blocks: async-stacks
Comment 2•5 years ago
|
||
I'm pretty sure this is a dup of bug 1601179. We're not consulting the realms' debuggee-ness everywhere we should.
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(jimb)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•