jMonkeyEngine / jMonkeyEngine/sdk
Assertion error when deleting native objects in the SDK
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 348
- Forks
- 104
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
From @Nehon on February 21, 2015 19:50
Sometime, I have this exception in the SDK
java.lang.AssertionError
at com.jme3.util.NativeObjectManager.deleteNativeObject(NativeObjectManager.java:140)
at com.jme3.util.NativeObjectManager.deleteUnused(NativeObjectManager.java:188)
at com.jme3.renderer.opengl.GLRenderer.postFrame(GLRenderer.java:853)
at com.jme3.system.lwjgl.LwjglOffscreenBuffer.runLoop(LwjglOffscreenBuffer.java:128)
at com.jme3.system.lwjgl.LwjglOffscreenBuffer.run(LwjglOffscreenBuffer.java:156)
[catch] at java.lang.Thread.run(Thread.java:745)
Can't reproduce it systematically though
Copied from original issue: jMonkeyEngine/jmonkeyengine#214
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing NativeObjectManager.deleteNativeObject at line 140 and deleteUnused at line 188, then follow the call path through GLRenderer.postFrame and LwjglOffscreenBuffer. Determine the lifecycle condition behind the intermittent AssertionError; done means its cause is reproducible or explained and the assertion no longer occurs during the affected offscreen run loop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100