1. Enter the Microsoft Developer Challenge for a chance to win prizes. Read more about it here.
  2. Enter the Google Play Indie Games Contest in Europe. Read more about it here.
  3. Unity 5.5 is now released.
  4. Become a closed-alpha partner on the new Facebook games platform. Read more about it here.
  5. Get early access to our Google Daydream Technical preview. Click here for more details!

Recieving CPU Pegged Error, Followed by Audio Flinger Output

Discussion in 'Android' started by akobylarek, Dec 21, 2011.

  1. akobylarek

    akobylarek

    Joined:
    Nov 18, 2009
    Messages:
    24
    SOLVED!
    For a reason unrelated to audio... It was because I was using the Self-Illum/Diffuse Shader.
    Removed everything from the scene and added it all back it until it didn't work.


    I am getting the output:
    Code (csharp):
    1. W/SharedBufferStack( 6257): waitForCondition(LockCondition) timed out (identity=188, status=0). CPU may be pegged. try again.
    about 6 times. The identity changes once.

    Immediately after this happens I get a output that says:

    Code (csharp):
    1. W/AudioFlinger(  73): write blocked for 71msecs, 53 delayed writes, thread 0x2f850.
    2. W/SharedBufferStack( 6257): waitForCondition(LockCondition) timed out (identity=188, status=0). CPU may be pegged. try again.
    3. W/SharedBufferStack( 6257): waitForCondition(LockCondition) timed out (identity=3, status=0). CPU may be pegged. try again.
    4. W/AudioFlinger(  73): stepServer failed acquiring cblk mutex.
    5. W/AudioFlinger(  73): stepServer recovered
    Then scene restarts (which it shouldn't), and it does it all over again.

    Anyone have any ideas. I tried taking all sound out of my scene because it is obviously failing somewhere in audio but I was wondering if anyone else had happened across this error and solved it.

    Thanks!
     
    Last edited: Dec 21, 2011
  2. akobylarek

    akobylarek

    Joined:
    Nov 18, 2009
    Messages:
    24
    Solved. See first post.
     
  3. leo26781

    leo26781

    Joined:
    Aug 28, 2012
    Messages:
    1
    HI ,

    I do get the same error . How did you solve the issue ?
     
    Last edited: Aug 28, 2012