Closed Bug 916773 Opened 11 years ago Closed 11 years ago

Initialize mLatency in SharedBuffer's constructor

Categories

(Core :: Web Audio, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla27
Tracking Status
firefox25 --- fixed
firefox26 --- fixed
firefox27 --- fixed

People

(Reporter: padenot, Assigned: padenot)

References

Details

(Whiteboard: [qa-])

Attachments

(1 file, 1 obsolete file)

      No description provided.
Attached file patch (obsolete) —
Attachment #805283 - Attachment is obsolete: true
Attachment #805283 - Attachment is patch: false
Attachment #805283 - Flags: review?(ehsan)
Comment on attachment 805285 [details] [diff] [review]
Initialize mLatency in SharedBuffer's constructor.

Review of attachment 805285 [details] [diff] [review]:
-----------------------------------------------------------------

Oops!
Attachment #805285 - Flags: review?(ehsan) → review+
Attachment #805283 - Flags: review?(ehsan)
Blocks: 908306
Blocks: 916135
Comment on attachment 805285 [details] [diff] [review]
Initialize mLatency in SharedBuffer's constructor.

[Approval Request Comment]
Bug caused by (feature/regressing bug #): bug 899135
User impact if declined: Unpredictable initial latency, when using WebAudio, suspected test timeout on b2g. This is important to have a solid WebAudio implementation.
Testing completed (on m-c, etc.): This is a trivial programming error (uninitialized variable).
Risk to taking this patch (and alternatives if risky): none.
String or IDL/UUID changes made by this patch: none.
Attachment #805285 - Flags: approval-mozilla-beta?
Attachment #805285 - Flags: approval-mozilla-aurora?
Do we have any evidence that this is responsible for the test timeouts in b2g?
(In reply to :Ehsan Akhgari (needinfo? me!) from comment #6)
> Do we have any evidence that this is responsible for the test timeouts in
> b2g?

Nothing experimental.  Just looking at the code, imagining what would happen with a large latency, and 908306 comment 11 observing that onaudioprocess is not called when a test times out.

There seem to have been some tests timing out even though they don't use ScriptProcessor, so this may not be the only issue on b2g.
https://hg.mozilla.org/mozilla-central/rev/425870d13b13
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
Comment on attachment 805285 [details] [diff] [review]
Initialize mLatency in SharedBuffer's constructor.

Doesn't meet the bar of needing uplift to Desktop/Mobile Firefox 25, good for Aurora and B2G 1.2 though
Attachment #805285 - Flags: approval-mozilla-beta?
Attachment #805285 - Flags: approval-mozilla-beta-
Attachment #805285 - Flags: approval-mozilla-aurora?
Attachment #805285 - Flags: approval-mozilla-aurora+
Comment on attachment 805285 [details] [diff] [review]
Initialize mLatency in SharedBuffer's constructor.

(In reply to comment #11)
> Comment on attachment 805285 [details] [diff] [review]
>   --> https://bugzilla.mozilla.org/attachment.cgi?id=805285
> Initialize mLatency in SharedBuffer's constructor.
> 
> Doesn't meet the bar of needing uplift to Desktop/Mobile Firefox 25, good for
> Aurora and B2G 1.2 though

This patch is almost as low-risk as a patch can possibly be, and it fixes a bug where we just read from garbage memory.  Can you please reconsider?  Thanks!
Attachment #805285 - Flags: approval-mozilla-beta- → approval-mozilla-beta?
Comment on attachment 805285 [details] [diff] [review]
Initialize mLatency in SharedBuffer's constructor.

Low risk early in the beta, not hugely against it.
Attachment #805285 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: