Closed Bug 853434 Opened 11 years ago Closed 11 years ago

crash in mozilla::dom::AudioBufferSourceNode::AudioBufferSourceNode

Categories

(Core :: Web Audio, defect)

x86
All
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla22

People

(Reporter: xtc4uall, Unassigned)

References

()

Details

(Keywords: crash, Whiteboard: [fixed by Bug 853076])

Crash Data

This bug was filed from the Socorro interface and is 
report bp-8cac4f87-295e-46eb-81bb-935cf2130321 .
============================================================= 

Got this non-reproducible Crash twice when trying the Testcase mentioned in Bug 779297 Comment 26 (on http://minimal.be/mozilla/decode/ and saved locally)

bp-a9dbf0e4-0719-402c-b1cb-7a2642130321 (clicked on "Play OGG file"; on Site)
bp-8cac4f87-295e-46eb-81bb-935cf2130321 (clicked on "Play WAV file"; local)

using Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20130320 Firefox/22.0 ID:20130320031103 CSet: 8156df33b757
Hardware: x86_64 → x86
Crash Signature: [@ mozilla::dom::AudioBufferSourceNode::AudioBufferSourceNode(mozilla::dom::AudioContext*)] → [@ mozilla::dom::AudioBufferSourceNode::AudioBufferSourceNode(mozilla::dom::AudioContext*)] [@ mozilla::MediaStream::Graph()]
OS: Windows 7 → All
Have you tested this on a build which has the fix for bug 853076?  I can't reproduce it on trunk, and I think bug 853076 might have fixed this...
Blocks: webaudio
(In reply to :Ehsan Akhgari (needinfo? me!) from comment #2)
> Have you tested this on a build which has the fix for bug 853076?  I can't
> reproduce it on trunk, and I think bug 853076 might have fixed this...

I do not appear to have this issue with the latest Nightly 22.0a1 (2013-03-23), so I imagine bug 853076 did.
Same over hee. Let's resolve this.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by Bug 853076]
Depends on: 853076
Target Milestone: --- → mozilla22
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.