Closed Bug 1071521 (dbg-trace) Opened 10 years ago Closed 9 years ago

[meta] Debugger tracing

Categories

(DevTools :: Debugger, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ejpbruel, Unassigned)

References

Details

No description provided.
Depends on: 950273
Depends on: 949928
Depends on: 949925
Depends on: 949909
Depends on: 949729
Depends on: 949726
Depends on: 949698
Depends on: 949694
Depends on: 951872
Depends on: 949924
Depends on: 949746
Alias: dbg-trace
Summary: [meta] Tracing → [meta] Debugger tracing
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools

A little piece of history as we revived yet another flavor of JS tracing.

This meta bug was tracking the very first tracing feature integrated into the old XUL debugger.
It has been removed in bug 1176981 (Firefox 42) because jstracelogger started in the JS engine.
I imagine that the plan was to move from Debugger API instrumentation to use the native jstracelogger.
Making the debugger tracer a bit obsolete and to be rewriten to use this new platform feature.
Instead of rewriting it, probably during the "great or dead" episode in Mozilla, this feature was removed.

Much later, the jstracelogger was removed from the JS engine in bug 1777529 (Firefox 104).
AFAIK, I think there is no more tracer for javascript in Firefox.
The profiler records JS but with sampling.

Recently, I re-introduced a very similar tracing feature in DevTools, using the same technique as the one tracked by this method,
using the Debugger API. bug 1803616 (Firefox 113).

Blocks: 1176981
See Also: → js-tracer
Depends on: 929349
You need to log in before you can comment on or make changes to this bug.