New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 639903 link

Starred by 2 users
Status: WontFix
Owner:
liber...@chromium.org
Closed: Nov 2016
Cc:
█ w...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

MediaCodecs might be released on the wrong thread if AVDA is destroyed before they're configured

Project Member Reported by w...@chromium.org, Aug 22 2016 
If AVDA is destroyed before its async configure completes, the MediaCodec is released on the main thread.

Have we seen any instances of freshly configured MediaCodecs hanging in release()? Or is it only after you've queued buffers? If the latter, this is a wontfix.

Comment 1 by w...@chromium.org, Aug 22 2016

Components: Internals>Media
Labels: OS-Android

Comment 2 by yini...@chromium.org, Aug 24 2016

Cc: -liber...@chromium.org
Owner: liber...@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by w...@chromium.org, Nov 21 2016

Status: WontFix (was: Assigned)
Haven't seen any instances of this crashing so I'm assuming it's safe until we see reports.
►

Sign in to add a comment