Closed
Bug 914392
Opened 11 years ago
Closed 9 years ago
Remove AudioNodeEngine::NodeMutex() usage
Categories
(Core :: Web Audio, defect, P3)
Tracking
()
RESOLVED
FIXED
mozilla42
Tracking | Status | |
---|---|---|
firefox42 | --- | fixed |
People
(Reporter: karlt, Assigned: karlt)
References
Details
Attachments
(3 files)
3.53 KB,
patch
|
padenot
:
review+
|
Details | Diff | Splinter Review |
6.16 KB,
patch
|
padenot
:
review+
|
Details | Diff | Splinter Review |
7.53 KB,
patch
|
padenot
:
review+
|
Details | Diff | Splinter Review |
Most clients of the NodeMutex() and AudioNode* Node() methods on AudioNodeEngine are calling from the main thread and so should be using NodeMainThread().
ProduceAudioBlock() in AnalyserNodeEngine and ScriptProcessorNodeEngine use NodeMutex() and Node() to check whether the node is alive before dispatching the event. This check is not necessary, because the event needs to handle the case of the Node getting destroyed before the event runs anyway.
Updated•11 years ago
|
Priority: -- → P3
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8633757 -
Flags: review?(padenot)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → karlt
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•9 years ago
|
||
so that it is always available.
Attachment #8633758 -
Flags: review?(padenot)
Assignee | ||
Comment 3•9 years ago
|
||
If DestroyMediaStream() has cleared the node on the engine, then it will call
MediaStream::Destroy(). I doubt the additional code and cost of repeatedly
checking this is worth the savings in no-op events dispatched to main thread
between MediaStream::Destroy() on the main thread and destruction on the graph
thread.
Also ScriptProcessorNode should not be potentially ignoring its output buffer
immediately when the ScriptProcessor loses its last reference. At least the
block currently being processed should output the output buffer.
(Deterministically playing the remainder of the output buffer would be best.)
Attachment #8633759 -
Flags: review?(padenot)
Assignee | ||
Comment 4•9 years ago
|
||
Updated•9 years ago
|
Attachment #8633757 -
Flags: review?(padenot) → review+
Updated•9 years ago
|
Attachment #8633758 -
Flags: review?(padenot) → review+
Updated•9 years ago
|
Attachment #8633759 -
Flags: review?(padenot) → review+
Comment 6•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/ad3370352602
https://hg.mozilla.org/mozilla-central/rev/d3818f780309
https://hg.mozilla.org/mozilla-central/rev/c7ddd289198c
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox42:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla42
You need to log in
before you can comment on or make changes to this bug.
Description
•