Exception in thread "jME3 Audio Decoder" java.lang.AssertionError
See original GitHub issueException in thread "jME3 Audio Decoder" java.lang.AssertionError
at com.jme3.audio.openal.ALAudioRenderer.updateInDecoderThread(ALAudioRenderer.java:1004)
at com.jme3.audio.openal.ALAudioRenderer.run(ALAudioRenderer.java:257)
at java.lang.Thread.run(Thread.java:748)
jme: 3.5.0-beta9, os: ubuntu/android fails because both statuses are ‘Paused’
I got this error multiple times in android emulator, then decided to reproduce it the desktop version… had to click play-pause ~50 times before it happened, possible a concurrency issue
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (5 by maintainers)
Top Results From Across the Web
What is the meaning of this "java.lang.IllegalStateException
java.lang.IllegalStateException: Decoding thread is terminated at com.jme3.audio.openal.ALAudioRenderer.checkDead(ALAudioRenderer.java:236)
Read more >Exception in thread "main" java.lang.AssertionError
It's a bug in the compiler because the class com.sun.tools.javac.util.Assert.error clearly says it's from javac , the Java compiler, ...
Read more >jmonkeyengine/ALAudioRenderer.java at master - GitHub
private static final String THREAD_NAME = "jME3 Audio Decoder"; ... throw new IllegalStateException("Decoding thread is terminated");.
Read more >Diff - refs/tags/android-6.0.1_r30^! - platform/external/jmonkeyengine
New drop of the jmonkeyengine library A new drop of the jmonkeyengine library sources, based on a 2012-03-05 snapshot. Fixes a few unnecessary...
Read more >assert that in java Code Example - Code Grepper
public static void main(String[] args) { int a = 6; assert a != 6 : "a != 6"; } //Exception in thread "main"...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Okay, thanks for that info. Your suggested fix sounds plausible to me. It’s unfortunate this issue missed the cut-off for 3.5.0-stable, but I expect we’ll fix it in the next release.
I reproduced this issue in the “v3.3” branch, so it’s not a regression and definitely not related to #1728.