Closed
Bug 1270055
Opened 9 years ago
Closed 9 years ago
Unaligned buffer used in DynamicsCompressor
Categories
(Core :: Web Audio, defect, P1)
Core
Web Audio
Tracking
()
RESOLVED
FIXED
mozilla49
Tracking | Status | |
---|---|---|
firefox46 | --- | unaffected |
firefox47 | --- | unaffected |
firefox48 | --- | wontfix |
firefox49 | --- | fixed |
People
(Reporter: dminor, Assigned: dminor)
References
Details
Attachments
(2 files)
This looks like what is causing this crash:
https://crash-stats.mozilla.com/report/index/fe2f58ec-0743-497e-9cd8-1ba2b2160503
Assignee | ||
Comment 1•9 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/50413/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/50413/
Attachment #8748607 -
Flags: review?(padenot)
Comment 2•9 years ago
|
||
Comment on attachment 8748607 [details]
MozReview Request: Bug 1270055 - Unaligned buffer used in DynamicsCompressor; r?padenot
https://reviewboard.mozilla.org/r/50413/#review47225
Attachment #8748607 -
Flags: review?(padenot) → review+
Comment 3•9 years ago
|
||
I guess we are missing tests for DynamicsCompressor with a Gain on the input.
Flags: in-testsuite?
Assignee | ||
Comment 5•9 years ago
|
||
This is also a bug in 48 but the alignment checks in AudioNodeEngine.cpp present in 48 prevent it from causing problems there, so I don't think it is worth fixing.
status-firefox46:
--- → unaffected
status-firefox47:
--- → unaffected
status-firefox48:
--- → wontfix
status-firefox49:
--- → affected
Assignee | ||
Updated•9 years ago
|
Rank: 20
Priority: -- → P1
Assignee | ||
Comment 6•9 years ago
|
||
Attachment #8749171 -
Flags: review?(karlt)
Assignee | ||
Updated•9 years ago
|
Attachment #8749171 -
Attachment is patch: true
Assignee | ||
Comment 7•9 years ago
|
||
Comment 8•9 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
Comment 9•9 years ago
|
||
Comment on attachment 8749171 [details] [diff] [review]
Test case with gain
Thanks, Dan!
I don't know what all these numbers mean. Can you add a comment, please, to
explain where the min and max peak values come?
I wouldn't worry, now that you have written this, but it would be good to put
new tests under testing/web-platform where appropriate. Even if the test is
more suitable for running only in Gecko, the testharness type (now the default
for gen_template.pl) is often better if no special powers are required,
because it can be easily ported to web-platform tests. testharness tests in
dom/media/webaudio run with the mochitests.
I never understood why so many web audio mochitests use addLoadEvent().
Attachment #8749171 -
Flags: review?(karlt) → review+
Assignee | ||
Comment 10•9 years ago
|
||
(In reply to Karl Tomlinson (ni?:karlt) from comment #9)
> Comment on attachment 8749171 [details] [diff] [review]
> Test case with gain
>
> Thanks, Dan!
>
> I don't know what all these numbers mean. Can you add a comment, please, to
> explain where the min and max peak values come?
>
Will do.
> I wouldn't worry, now that you have written this, but it would be good to put
> new tests under testing/web-platform where appropriate. Even if the test is
> more suitable for running only in Gecko, the testharness type (now the
> default
> for gen_template.pl) is often better if no special powers are required,
> because it can be easily ported to web-platform tests. testharness tests in
> dom/media/webaudio run with the mochitests.
>
> I never understood why so many web audio mochitests use addLoadEvent().
Thanks for the tip. I've been cargo-culting existing mochitests when making new tests, I'll look at switching over to testharness tests next time.
Comment 11•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Flags: in-testsuite? → in-testsuite+
Comment 12•9 years ago
|
||
bugherder |
You need to log in
before you can comment on or make changes to this bug.
Description
•