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

Issue 627259 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

[FATAL:opensles_output.cc(336)] Check failed: delay >= 0 (-3119300 vs. 0)

Project Member Reported by w...@chromium.org, Jul 11 2016

Issue description

Saw this on a debug build of M52 on a JB Galaxy Nexus.

I believe I was entering fullscreen when it happened. I wasn't able to get a useful stack trace from the logs for some reason.

07-11 14:55:41.241  3146  3300 F libc    : Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 3300 (AudioTrack)
07-11 14:55:41.249   119   119 I DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-11 14:55:41.249   119   119 I DEBUG   : Build fingerprint: 'google/mysid/toro:4.1.1/JRO03O/424425:user/release-keys'
07-11 14:55:41.249   119   119 I DEBUG   : pid: 3146, tid: 3300, name: AudioTrack  >>> org.chromium.chrome <<<
07-11 14:55:41.249   119   119 I DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
07-11 14:55:41.522   119   119 I DEBUG   : 
07-11 14:55:41.522   119   119 I DEBUG   : backtrace:
07-11 14:55:41.522   119   119 I DEBUG   :     #00  pc 000180ae  /system/lib/libc.so
07-11 14:55:41.522   119   119 I DEBUG   :     #01  pc 0000dbd4  /system/lib/libc.so (abort+4)
07-11 14:55:41.522   119   119 I DEBUG   :     #02  pc 029aade5  /data/data/org.chromium.chrome/lib/libchrome.so

 
Hmm, if it's reliable we'll have to clamp to zero or disable on jellybean.

Comment 2 by w...@chromium.org, Jul 11 2016

I've seen it probably five times in 15 minutes of usage. 
Cc: -dalecur...@chromium.org
Owner: dalecur...@chromium.org
Status: Started (was: Available)
Project Member

Comment 4 by bugdroid1@chromium.org, Jul 13 2016

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

commit 9ed5f67fdb5b313f3d26e612615ae4812f411620
Author: dalecurtis <dalecurtis@chromium.org>
Date: Wed Jul 13 22:54:00 2016

Pick up starting position from OpenSLES getPosition().

On older versions of Android it looks like getPosition() does not
return to zero after Clear() is called; so we must pick up the
initial position returned from getPosition() in order to calculate
the delay for our audio stream.

For posterity, I tried calling ClearMarkerPosition(),
SetPositionUpdatePeriod(), and various contortions of using the
returned position without any success. Including continuing to
use the last known position if the starting-position is non-zero.

BUG= 627259 
TEST=no dcheck.

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

[modify] https://crrev.com/9ed5f67fdb5b313f3d26e612615ae4812f411620/media/audio/android/opensles_output.cc

Labels: M-54
Status: Fixed (was: Started)
JB should be disabled on M52, M53, so not merging back.

Sign in to add a comment