Open
Bug 1144358
Opened 9 years ago
Updated 2 years ago
Double-counting |ThreadSharedFloatArrayBufferList| in |AudioBufferSourceNode|
Categories
(Core :: Web Audio, defect, P4)
Tracking
()
NEW
People
(Reporter: JanH, Unassigned)
References
()
Details
(Whiteboard: [MemShrink:P2])
Attachments
(1 file)
349.95 KB,
application/x-bzip2
|
Details |
Similar to bug 1074387, I've found another instance where memory in webaudio seems to get double-counted. If I load up a song in The Infinite Jukebox (e.g. http://labs.echonest.com/Uploader/index.html?trid=TRDUQAQ14B46F9D0FF) and start playback, each time the playback position jumps to a different spot in the song, the memory reported for explicit/webaudio/audio-node/AudioBufferSourceNode/dom-nodes increases a bit, until it first causes heap-unclassified to turn negative and then finally exceeds the total amount reported for explicit memory. I've tested this with FF36.0.1 on Windows and FF36.0.2 and the current Nightly on Android.
Updated•9 years ago
|
Component: Video/Audio → Web Audio
Whiteboard: [MemShrink]
Comment 2•9 years ago
|
||
It looks like the |ThreadSharedFloatArrayBufferList| in |AudioBufferSourceNode| is being double counted.
Updated•9 years ago
|
Summary: Double-counting of memory in webaudio → Double-counting |ThreadSharedFloatArrayBufferList| in |AudioBufferSourceNode|
Comment 3•9 years ago
|
||
AudioBuffer and OscillatorNodeEngine may have the same issue. ConvolverNodeEngine and PeriodicWave guard on !mBuffer->IsShared() to prevent double counting. AudioBufferSourceNodeEngine does not seem to try to measure it. At least, that's at a lose audit of code that has a reference to this class.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•9 years ago
|
||
The sizeof method for the buffer list could assert if IsShared is true maybe?
Updated•9 years ago
|
Whiteboard: [MemShrink] → [MEMSHRINK:P2]
Updated•9 years ago
|
Whiteboard: [MEMSHRINK:P2] → [MemShrink:P2]
Updated•9 years ago
|
Priority: -- → P3
Comment 5•7 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Updated•5 years ago
|
Assignee: erahm → nobody
Updated•2 years ago
|
Severity: minor → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•