Closed
Bug 1903791
Opened 2 years ago
Closed 2 years ago
Increate js tracer max depth and make it configurable
Categories
(DevTools :: Debugger, enhancement)
DevTools
Debugger
Tracking
(firefox129 fixed)
RESOLVED
FIXED
129 Branch
| Tracking | Status | |
|---|---|---|
| firefox129 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
Details
Attachments
(1 file)
When tracing https://beta--mozilla-perfcompare.netlify.app/ or the profiler frontend, you quickly reach the infinite loop restriction, which stops the tracer when the depth of execution is higher than 100.
Let's increase this limit and make it configurable via a preference.
| Assignee | ||
Comment 1•2 years ago
|
||
When a JS stack is longer than this 200 limit, the tracer will automatically stop and consider
the current execution as an infinite loop.
Updated•2 years ago
|
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/39e9da228aad
[devtools] Increase max-depth tracer limit and make it configurable via a preference. r=devtools-reviewers,nchevobbe
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox129:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 129 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•