New issue
Advanced search Search tips

Issue 640793 link

Starred by 2 users
Status: Verified
Owner:
hongchan@chromium.org
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Use WorkerPool for AudioContext.decodeAudioData()

Project Member Reported by hongchan@chromium.org, Aug 24 2016 
Currently the audio context always instantiates a dedicated thread for AsyncAudioDecoder class. Use WorkerPool instead.
Project Member

Comment 1 by bugdroid1@chromium.org, Sep 1 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/54ff0fdf2b744504617959819fc00d38538da647

commit 54ff0fdf2b744504617959819fc00d38538da647
Author: hongchan <hongchan@chromium.org>
Date: Thu Sep 01 22:54:11 2016

Use background thread for AsyncAudioDecoder

With the creation of BaseAudioContext, an additional thread dedicated to
AsyncAudioDecoder is also instantiated. This design is sub-optimal and we
can use the background thread (i.e. WorkerPool) for this purpose.

BUG= 640793 
TEST=NONE (all the decoder-related layout test passes)

Review-Url: https://codereview.chromium.org/2268403006
Cr-Commit-Position: refs/heads/master@{#416100}

[modify] https://crrev.com/54ff0fdf2b744504617959819fc00d38538da647/third_party/WebKit/Source/modules/webaudio/AsyncAudioDecoder.cpp
[modify] https://crrev.com/54ff0fdf2b744504617959819fc00d38538da647/third_party/WebKit/Source/modules/webaudio/AsyncAudioDecoder.h

Comment 2 by hongchan@chromium.org, Oct 3 2016

Status: Verified (was: Started)
►

Sign in to add a comment