Closed Bug 1663975 Opened 5 years ago Closed 4 years ago

Consider disallowing running JS earlier in shutdown

Categories

(Core :: XPConnect, enhancement, P3)

Product:
Core
Component:
XPConnect
Type:
enhancement

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: mccr8, Unassigned)

References

Details

I've seen at least a few beta-only crashes that happen because we're running chrome JS very late in XPCOM shutdown, after ClearOnShutdown() has cleared pointers. For instance bug 1663315 and bug 1656973. These seem like old issues, but they've only started happening recently for some reason.

In a review comment in my patch on bug 1663315, kmag pointed out that it seems bad that we're running chrome JS at all this late, so maybe we should just disallow it at some point. I don't know what might break. I'll file another bug on the XPCOM side of the late-running chrome JS issue.

See Also: → 1663981
QA Whiteboard: qa-not-actionable
Severity: S2 → S3

Somebody can file a new issue if they want to look into this. I just had kind of a vague idea and never followed up with it.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.