Move SetTimeout/Interval firing-order assertion to DIAGNOSTIC_ASSERT

RESOLVED FIXED in Firefox 67

Status

()

enhancement
RESOLVED FIXED
5 months ago
4 months ago

People

(Reporter: jesup, Assigned: jesup)

Tracking

(Depends on 1 bug)

52 Branch
mozilla67
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox67 fixed)

Details

Attachments

(1 attachment)

We have indications that rarely this assertion can fail, but can't get a reproducible case. Moving the assertion to MOZ_DIAGNOSTIC_ASSERT to try to make sure we catch it, and that it's not breaking sites anywhere.

If when this lands we get any significant hitrate on it, I'll likely back the patch out until we resolve the problem.  I don't expect that, but it's possible.  DIAGNOSTIC_ASSERT to ensure we can't accidentally ship this.
Attachment #9044337 - Flags: review?(bugs)
Comment on attachment 9044337 [details] [diff] [review]
Move a DOM timeout spec-compliance ASSERT to DIAGNOSTIC_ASSERT

(and r+ if you need to back this out quickly to keep Nightlies working, though need to then also figure out what is wrong with timers)
Attachment #9044337 - Flags: review?(bugs) → review+
Pushed by rjesup@wgate.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f8058a73d119
Move a DOM timeout spec-compliance ASSERT to DIAGNOSTIC_ASSERT r=smaug
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
Depends on: 1528620
Backout by rjesup@wgate.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/eb69f933e572
Backed out changeset f8058a73d119 r=smaug
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.