Closed
Bug 839753
Opened 13 years ago
Closed 13 years ago
Setting expando on AudioContext destination causes bad things
Categories
(Core :: Audio/Video, defect)
Tracking
()
RESOLVED
FIXED
mozilla21
People
(Reporter: jruderman, Assigned: mccr8)
Details
(Keywords: assertion, crash, testcase)
Attachments
(2 files, 1 obsolete file)
|
64 bytes,
text/html
|
Details | |
|
3.17 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
With
user_pref("media.webaudio.enabled", true);
###!!! ASSERTION: Cycle collection participant didn't traverse to preserved wrapper! This will probably crash.: 'callback.mFound', file content/base/src/nsContentUtils.cpp, line 6128
###!!! ASSERTION: Cycle collection participant didn't trace preserved wrapper! This will probably crash.: 'callback.mFound', file content/base/src/nsContentUtils.cpp, line 6134
Assertion failure: !PreservingWrapper() (Clearing a preserved wrapper!), at ../../../dom/base/nsWrapperCache.h:112
| Assignee | ||
Comment 1•13 years ago
|
||
The QI for AudioDestinationNode looks wrong to me. I don't see how it is going to produce the CC participant. I think this is another thing that would be caught by bug 614238.
This is a regression from the bug landed as bug 804837, but I'm not sure what the real bug number was.
| Assignee | ||
Comment 2•13 years ago
|
||
I can fix this on Monday, anybody else should feel free to fix it earlier if they want to.
Assignee: nobody → continuation
| Assignee | ||
Comment 3•13 years ago
|
||
| Assignee | ||
Comment 4•13 years ago
|
||
Attachment #712685 -
Attachment is obsolete: true
Attachment #712941 -
Flags: review?(bugs)
Comment 5•13 years ago
|
||
Comment on attachment 712941 [details] [diff] [review]
tested locally, added test
We can do this, but I wonder why AudioNode isn't wrapperCached.
Attachment #712941 -
Flags: review?(bugs) → review+
| Assignee | ||
Comment 6•13 years ago
|
||
It used to be, but the patch that broke this intentionally made it so that only destination is. I'm not sure what the actual bug was where that happened, so I'm not sure why exactly.
That is intentional (and correct). We need to allow the JS binding to be GCed so we can determine that there's no longer any way the AudioNode can produce output in the future (then we can optimize it away).
| Assignee | ||
Updated•13 years ago
|
Keywords: checkin-needed
Comment 8•13 years ago
|
||
Flags: in-testsuite+
Keywords: checkin-needed
Comment 9•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
You need to log in
before you can comment on or make changes to this bug.
Description
•