Closed
Bug 1223734
Opened 9 years ago
Closed 9 years ago
"Assertion failure: false (Should not have an existing pref cache for this address)" - 'dom.audiochannel.mutedByDefault' - #2
Categories
(Core :: Audio/Video, defect)
Core
Audio/Video
Tracking
()
RESOLVED
FIXED
mozilla45
Tracking | Status | |
---|---|---|
firefox45 | --- | fixed |
People
(Reporter: jruderman, Assigned: baku)
Details
(Keywords: assertion, testcase)
Attachments
(5 files, 3 obsolete files)
306 bytes,
text/html
|
Details | |
5.13 KB,
text/plain
|
Details | |
11.26 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
1.66 KB,
patch
|
Details | Diff | Splinter Review | |
1.73 KB,
patch
|
baku
:
review+
|
Details | Diff | Splinter Review |
This is basically the same testcase as bug 1187204, but with the statements in a different order.
1. Disable e10s
2. Load the testcase
3. Quit Firefox
Result:
Attempt to add a bool pref cache for preference 'dom.audiochannel.mutedByDefault' at address '0x10b4c34c8'was made. However, a pref was already cached at this address.
Assertion failure: false (Should not have an existing pref cache for this address), at /Users/jruderman/trees/mozilla-central/modules/libpref/Preferences.cpp:216
Reporter | ||
Comment 1•9 years ago
|
||
Assignee | ||
Comment 2•9 years ago
|
||
Or... we should implement a NS_AreWeShuttingdown
Assignee: nobody → amarchesini
Attachment #8686082 -
Flags: review?(bugs)
Comment 3•9 years ago
|
||
Comment on attachment 8686082 [details] [diff] [review]
acs.patch
So AudioChannelAgent::NotifyStoppedPlaying() will crash with this change based on the stack
Attachment #8686082 -
Flags: review?(bugs) → review-
Assignee | ||
Comment 4•9 years ago
|
||
Attachment #8686082 -
Attachment is obsolete: true
Attachment #8686150 -
Flags: review?(bugs)
Comment 5•9 years ago
|
||
Comment on attachment 8686150 [details] [diff] [review]
acs.patch
So nothing guarantees the raw pointers in mSpeakerManager are clearer properly.
Attachment #8686150 -
Flags: review?(bugs) → review+
Assignee | ||
Comment 6•9 years ago
|
||
Attachment #8686150 -
Attachment is obsolete: true
Attachment #8686165 -
Flags: review?(bugs)
Assignee | ||
Comment 7•9 years ago
|
||
Attachment #8686166 -
Flags: review?(bugs)
Comment 8•9 years ago
|
||
Comment on attachment 8686166 [details] [diff] [review]
xpcom.patch
I do like something like this and have long wondered why we don't have this, but Nathan should review this.
+ * Return true if we are shutting down. Means if NS_ShutdownXPCOM has been
+ * called.
isn't quite accurate. gXPCOMShuttingDown is set to true quite late (oddly late, I'd say) during shutdown.
Attachment #8686166 -
Flags: review?(nfroyd)
Attachment #8686166 -
Flags: review?(bugs)
Attachment #8686166 -
Flags: feedback+
Updated•9 years ago
|
Attachment #8686165 -
Flags: review?(bugs) → review+
Assignee | ||
Comment 9•9 years ago
|
||
Attachment #8686166 -
Attachment is obsolete: true
Attachment #8686166 -
Flags: review?(nfroyd)
Attachment #8686219 -
Flags: review?(nfroyd)
Comment 10•9 years ago
|
||
Comment on attachment 8686219 [details] [diff] [review]
xpcom.patch
Review of attachment 8686219 [details] [diff] [review]:
-----------------------------------------------------------------
Looks to me like AudioChannelService is already listening for the xpcom-shutdown observer notification, so it should just be setting a flag that says we shouldn't create any more AudioChannelService instances? That would also avoid the problem of there being a significant lag between xpcom-shutdown and gXPCOMShuttingDown/NS_IsXPCOMShuttingDown() and AudioChannelService being reinstantiated somewhere in the middle of that.
Attachment #8686219 -
Flags: review?(nfroyd)
Assignee | ||
Comment 11•9 years ago
|
||
What Nathan says makes sense to me. I land a previous version of this patch, already reviewed by smaug:
https://hg.mozilla.org/integration/mozilla-inbound/rev/b22d1abe0289
Comment 12•9 years ago
|
||
We discussed this on IRC a bit today. Jesse's take was that the testcase was likely to manifest as an intermittent failure at best when run as part of our test infrastructure (since we don't have a good story for testing shutdown issues and forcing a GC was enough to make this problem go away locally). And on Try, this testcase is indeed green across the board both before and after the patch in this bug landed.
That said, landing fuzzer testcases gives more fodder for future fuzzing, so I think the pros (as miniscule as they appear to be) outweigh the cons here. What do you think, Andrea?
https://treeherder.mozilla.org/#/jobs?repo=try&revision=574b0aa54e8d&group_state=expanded
Attachment #8688117 -
Flags: review?(amarchesini)
Updated•9 years ago
|
Attachment #8688117 -
Attachment is patch: true
Assignee | ||
Comment 13•9 years ago
|
||
Comment on attachment 8688117 [details] [diff] [review]
crashtest-ized version of the testcase
Review of attachment 8688117 [details] [diff] [review]:
-----------------------------------------------------------------
I agree with you. Nice to know I can write such tests.
Attachment #8688117 -
Flags: review?(amarchesini) → review+
Comment 14•9 years ago
|
||
Updated•9 years ago
|
Flags: in-testsuite+
Comment 15•9 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
Comment 16•9 years ago
|
||
bugherder |
You need to log in
before you can comment on or make changes to this bug.
Description
•