Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

OpenALException: Invalid Device during app intialization on Windows

See original GitHub issue

I recently began seeing this crash with software/hardware that used to work. I suspect it’s caused by misconfiguration and/or failing hardware on my Window 7 system. Last time I fixed it by changing the default audio device. This time, I want to document the stack trace:

AL lib: (EE) DoReset: Failed to initialize audio client: 0x887c0032
Jul 25, 2019 8:31:18 PM com.jme3.app.LegacyApplication handleError
SEVERE: Uncaught exception thrown in Thread[jME3 Main,5,main]
org.lwjgl.openal.OpenALException: Invalid Device
	at org.lwjgl.openal.Util.checkALCError(Util.java:55)
	at org.lwjgl.openal.ALC10.alcCreateContext(ALC10.java:251)
	at org.lwjgl.openal.AL.init(AL.java:173)
	at org.lwjgl.openal.AL.create(AL.java:143)
	at org.lwjgl.openal.AL.create(AL.java:102)
	at org.lwjgl.openal.AL.create(AL.java:206)
	at com.jme3.audio.lwjgl.LwjglALC.createALC(LwjglALC.java:15)
	at com.jme3.audio.openal.ALAudioRenderer.initOpenAL(ALAudioRenderer.java:95)
	at com.jme3.audio.openal.ALAudioRenderer.initialize(ALAudioRenderer.java:225)
	at com.jme3.app.LegacyApplication.initAudio(LegacyApplication.java:283)
	at com.jme3.app.LegacyApplication.initialize(LegacyApplication.java:602)
	at com.jme3.app.SimpleApplication.initialize(SimpleApplication.java:178)
	at com.jme3.system.lwjgl.LwjglAbstractDisplay.initInThread(LwjglAbstractDisplay.java:130)
	at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:211)
	at java.lang.Thread.run(Thread.java:748)

Issue Analytics

State:
Created 4 years ago
Comments:16 (8 by maintainers)

Top GitHub Comments

1reaction

cosmicchipsocketcommented, Feb 15, 2020

Not a jMonkeyEngine user but today someone reported what appaears to be the same OpenAL issue with my own engine. They were able to work around the issue by unplugging their headphones (although the OpenAL device name reported “OpenAL Soft on Speakers (Conexant SmartAudio HD)”).

AL lib: (EE) ALCwasapiPlayback_resetProxy: Failed to check format support: 0x80040154
AL lib: (EE) ALCwasapiPlayback_resetProxy: Failed to initialize audio client: 0x80070006

Subscribing to this issue in case someone figures it out.

1reaction

wouteriocommented, Sep 18, 2019

If you can no longer reproduce the issue then I guess you fixed it… 😛

Anyway, I can test the fix for the scenario I mentioned earlier, if I know where to get your fix from.

Top Results From Across the Web

Error codes in Device Manager in Windows - Microsoft Support

In the device's Properties dialog box, click the Driver tab, and then click Uninstall. Follow the instructions. Restart your computer. Open Device Manager, ......

.NET Framework initialization errors: Managing the user ...

This situation typically occurs when an application requires a CLR version that is invalid or not installed on a given computer. If the ......

Troubleshoot the TPM (Windows) | Microsoft Learn

Open the Windows Defender Security Center app. Select Device security. Select Security processor details. Select Security processor ...

System Error Codes (1000-1299) (WinError.h) - Win32 apps

No serial device was successfully initialized. The serial driver will unload. ERROR_IRQ_BUSY. 1119 (0x45F). Unable to open ...

Microsoft .Net Framework error "Unhandled exception has ...

Unhandled exception has occurred in your application. ... Configuration system failed to initialize ---> System.Configuration.