Closed
Bug 1353502
Opened 7 years ago
Closed 7 years ago
nsContentUtils::RemoveScriptBlocker() shouldn't have diagnostic asserts
Categories
(Core :: DOM: Core & HTML, enhancement)
Tracking
()
RESOLVED
FIXED
mozilla55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
Details
Attachments
(1 file)
630 bytes,
patch
|
qdot
:
review+
|
Details | Diff | Splinter Review |
http://searchfox.org/mozilla-central/rev/381a7b8f8a78b481336cfa384cb0a5536e217e4a/dom/base/nsContentUtils.cpp#5329 shows up in all the DOM profiles.
Assignee | ||
Comment 1•7 years ago
|
||
The diagnostic assert makes profiling Nightly more difficult. And I haven't seen it catching any issues ever. I do assume we crash anyhow very quickly if one is using script blockers off the main thread
Assignee: nobody → bugs
Attachment #8854553 -
Flags: review?(kyle)
Assignee | ||
Comment 2•7 years ago
|
||
And commit message could be -m "Bug 1353502 - nsContentUtils::RemoveScriptBlocker() shouldn't have diagnostic asserts since such show up in performance profiles, r=qDot"
Updated•7 years ago
|
Attachment #8854553 -
Flags: review?(kyle) → review+
Pushed by opettay@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/1c0d3fedaa67 nsContentUtils::RemoveScriptBlocker() shouldn't have diagnostic asserts since such show up in performance profiles, r=qDot
Comment 4•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1c0d3fedaa67
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•