If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

WebAudio Assertion failure: mWriteIndex < mLength (How did this happen?) [@mozilla::dom::OfflineDestinationNodeEngine::ProduceAudioBlock]

RESOLVED FIXED in mozilla24

Status

()

Core
Web Audio
--
critical
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: posidron, Assigned: Ehsan)

Tracking

(Blocks: 1 bug, {assertion, crash, testcase})

Trunk
mozilla24
x86_64
Mac OS X
assertion, crash, testcase
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments, 1 obsolete attachment)

(Reporter)

Description

4 years ago
Created attachment 755449 [details]
testcase

I have marked this as s-s because it is similar to bug 877125.

Tested with m-i http://hg.mozilla.org/integration/mozilla-inbound/rev/bd9e82e152d5
(Reporter)

Comment 1

4 years ago
Created attachment 755450 [details]
callstack
(Reporter)

Comment 2

4 years ago
Created attachment 755453 [details]
testcase
(Reporter)

Updated

4 years ago
Attachment #755449 - Attachment is obsolete: true
This is not really a security bug.  Nothing bad actually happens in this case, it's just a bogus assertion.

That being said, it doesn't make sense to make it possible to create offline contexts with a length of zero, so we should just disallow that, I think.
Group: core-security
Created attachment 755598 [details] [diff] [review]
Patch (v1)
Assignee: nobody → ehsan
Status: NEW → ASSIGNED
Attachment #755598 - Flags: review?(roc)
Attachment #755598 - Flags: review?(roc) → review+
http://hg.mozilla.org/integration/mozilla-inbound/rev/07d2a8c94bda
https://hg.mozilla.org/mozilla-central/rev/07d2a8c94bda
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla24
Mass moving Web Audio bugs to the Web Audio component.  Filter on duckityduck.
Component: Video/Audio → Web Audio
You need to log in before you can comment on or make changes to this bug.