App crashed during testing 295.5 ROBO - Banks.SoundPoolManager$SoundSettings.left

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.
  • Hi,

    ROBO tests by Googles' Firebase found some issue with my build (made with 295.5). Any ideas? Log file is Please login to see this link.


    Fatal exception

    java.lang.NullPointerException: Attempt to write to field 'float Banks.SoundPoolManager$SoundSettings.left' on a null object reference in method 'void Banks.SoundPoolManager$2.run()'

    FATAL EXCEPTION: pool-10-thread-1
    Process: achhobby.pumpkins.com, PID: 20585
    java.lang.NullPointerException: Attempt to write to field 'float Banks.SoundPoolManager$SoundSettings.left' on a null object reference in method 'void Banks.SoundPoolManager$2.run()'
    at Banks.SoundPoolManager$2.run(SoundPoolManager.java:167)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
    at java.lang.Thread.run(Thread.java:1012)
    FATAL EXCEPTION: pool-10-thread-2
    Process: achhobby.pumpkins.com, PID: 20585
    java.lang.NullPointerException: Attempt to write to field 'float Banks.SoundPoolManager$SoundSettings.left' on a null object reference in method 'void Banks.SoundPoolManager$2.run()'
    at Banks.SoundPoolManager$2.run(SoundPoolManager.java:167)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
    at java.lang.Thread.run(Thread.java:1012)

  • Hi,

    I ran the newer runtime (0831) and the issue above was resolved. Now Google's console reports a new issue (65% of the crashes):

    Exception java.lang.OutOfMemoryError: Could not allocate JNI Env: Failed anonymous mmap(0x0, 8192, 0x3, 0x22, -1, 0): Operation not permitted. See process maps in the log.
    at java.lang.Thread.nativeCreate
    at java.lang.Thread.start (Thread.java:883)
    at java.util.concurrent.ThreadPoolExecutor.addWorker (ThreadPoolExecutor.java:975)
    at java.util.concurrent.ThreadPoolExecutor.execute (ThreadPoolExecutor.java:1382)
    at Banks.CSound.runBg (CSound.java:94)
    at Banks.CSound.start (CSound.java:450)
    at Application.CSoundPlayer.play (CSoundPlayer.java:254)
    at Actions.ACT_PLAYCHANNEL.execute (ACT_PLAYCHANNEL.java:48)
    at Events.CEventProgram.call_Actions (CEventProgram.java:2091)
    at Events.CEventProgram.computeEventList (CEventProgram.java:1874)
    at RunLoop.CRun.f_GameLoop (CRun.java:5715)
    at RunLoop.CRun.doRunLoop (CRun.java:603)
    at Application.CRunApp.loopFrame (CRunApp.java:1125)
    at Application.CRunApp.playApplication (CRunApp.java:831)
    at Application.CRunTimerTask.run (CRunTimerTask.java:53)
    at android.os.Handler.handleCallback (Handler.java:883)
    at android.os.Handler.dispatchMessage (Handler.java:100)
    at android.os.Looper.loop (Looper.java:214)
    at android.app.ActivityThread.main (ActivityThread.java:7398)
    at java.lang.reflect.Method.invoke
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:492)
    at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:980)


  • Yes, there is a memory leak on games that concurrent use sounds as shooting games.

    I will send you by PM a link with new beta.

    Regards,


    Fernando Vivolo

    ... new things are coming ...

  • IIRC there are fixes in the sound pool manager for the next build (some crashes where fixed in the build 295.5 but it was an incomplete fix). Should be fixed in build 295.6.

    Do you have any predictions for the launch of the 295.6?
    thanks.

    Nin - Ten - Do

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!