If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Lots of JSTracer goop left in the tree

RESOLVED INVALID

Status

()

Core
JavaScript Engine
RESOLVED INVALID
6 years ago
6 years ago

People

(Reporter: RyanVM, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

6 years ago
Looking at mxr, it appears that there's a lot of JSTracer stuff left in the tree. Shouldn't it all be gone now?
(Reporter)

Updated

6 years ago
OS: Windows 7 → All
Hardware: x86_64 → All
This is some unfortunate overloading, the JSTracer class keeps track of state during GC marking and doesn't have anything to do with the trace JIT.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
JSTracer is used for tracing roots for the GC. We always had this kind of ambiguity, luckily the tracing jit is gone now.
Brain beat me to it ;)
Oops, sorry, Ryan, I should have remembered that when you brought up JSTracer in IRC, I just totally spaced out there...
You need to log in before you can comment on or make changes to this bug.