jMonkeyEngine / jMonkeyEngine/jmonkeyengine
cryptic crash caused by jme3-jogg library absent at runtime
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 14
Description
Raised at the Forum/Hub: https://hub.jmonkeyengine.org/t/why-this-exception-appears/44890
Surely we can provide a more helpful diagnostic!
How to reproduce the crash:
In "jme3-examples/build.gradle", replace
implementation project(':jme3-jogg')
with
compileOnly project(':jme3-jogg')
and then run one of the audio tests, such as "TestOgg".
Typical console output, for current "master" branch:
Playing without filter
Sep 06, 2021 9:12:57 AM com.jme3.app.LegacyApplication handleError
SEVERE: Uncaught exception thrown in Thread[jME3 Main,6,main]
com.jme3.asset.AssetLoadException: No loader registered for type "ogg"
at com.jme3.asset.ImplHandler.aquireLoader(ImplHandler.java:196)
at com.jme3.asset.DesktopAssetManager.loadLocatedAsset(DesktopAssetManager.java:268)
at com.jme3.asset.DesktopAssetManager.loadAsset(DesktopAssetManager.java:388)
at com.jme3.audio.AudioNode.<init>(AudioNode.java:164)
at com.jme3.audio.AudioNode.<init>(AudioNode.java:144)
at jme3test.audio.TestOgg.simpleInitApp(TestOgg.java:53)
Contributor guide
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
Reproduce the failure by changing the dependency in jme3-examples/build.gradle and running an audio test such as TestOgg. Start at com.jme3.asset.ImplHandler.aquireLoader, following the stack trace from DesktopAssetManager to AudioNode. Done means the missing jme3-jogg case produces a more helpful diagnostic than the current "No loader registered for type ogg" message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100