Re: Jelly Bean on Nexus 7: AudioFlinger(126): no more track names available

[Glenn Kasten]

Follow-ups at https://groups.google.com/d/topic/android-platform/tyITQ09vV3s/discussion 

On Monday, August 13, 2012 9:07:07 PM UTC-7, brooker wrote:

My question is related to the following topic which discusses max number of AudioTracks:

https://groups.google.com/d/msg/android-platform/tyITQ09vV3s/jwNdyI2-7iYJ

We're effectively creating and later releasing AudioTracks in response to touches on the display.  We keep the set to about 14, but for short periods it may go up to 18 or so.

We haven't had a problem with any devices on any versions of the OS until Jelly Bean on Nexus 7.  Now we're getting the following:

08-13 20:55:33.253: E/AudioFlinger(126): no more track names available

08-13 20:55:33.253: E/AudioTrack(2492): AudioFlinger could not create track, status: -12

08-13 20:55:33.253: E/AudioTrack-JNI(2492): Error initializing AudioTrack

08-13 20:55:33.253: E/AudioTrack-Java(2492): [ android.media.AudioTrack ] Error code -20 when initializing AudioTrack.

1) When calling release, is it really releasing the track name? Are there situations where it not be releasing the name?

2) Is there a way to track the track name allocations?

3) Any idea if there were any changes in Jelly Bean, or any implementation details in the Nexus 7 which may be causing this?