Some sounds effects are more like white noise or crackling sound. Eventually minecraft-client will crash with libopenal.so being the culprit. Compiling with pulseaudio backend and forcing it to use that make no difference. Playing music or video in Firefox works fine (non-openal stuff). Reverting openal-soft to 18.2 solves the issue. This with 12-ALPHA8 on Intel Kabylake laptop.
(In reply to Johannes Lundberg from comment #0) What makes you think that this is a problem in openal and not some undefined behavior in lwjgl that now shows itself? A stack trace would be nice. Are other applications using openal-soft affected? Try running altonegen (it should output a normal sine wave). You could also try mpv built with OPENAL=on. Use 'mpv -ao openal' to select the OpenAL backend. If you have a ~/.alsoftrc or /usr/local/etc/openal-soft/alsoftrc try moving them out of the way too.
Yeah you're right. mpv plays fine with openal so it might be that lwjgl expects 18.2.
Over to games/lwjgl maintainer.
I've seen the same crash in games/0ad and openal-soft 1.19.0 on 12.0-BETA3. I did not have this problem when using openal-soft 1.18.2. Here's the stack trace: (lldb) bt * thread #1, name = 'alsoft-mixer', stop reason = signal SIGSEGV * frame #0: 0x0000000801d9f7e0 libopenal.so.1`___lldb_unnamed_symbol495$$libopenal.so.1 + 496
And here's a similar bug report from Arch Linux. I think it's an OpenAL bug. https://www.reddit.com/r/wine_gaming/comments/9f3w0g/hearing_loud_pops_in_left_audio_channel_since/
Does openal-soft 1.19.1 work better for you? Please compile openal-soft with debugging symbols (make WITH_DEBUG=) to hopefully get a better stacktrace. At the moment it's not very helpful.
So far openal-soft 1.19.1 is working bug-free. I'd lasted a lot longer than 1.19.0 did.
(In reply to Alan Somers from comment #7) > So far openal-soft 1.19.1 is working bug-free. I'd lasted a lot longer than > 1.19.0 did. Any more problems? Has anybody retested lwjgl against openal-soft 1.19.1 ?
Still no problems with 1.19.1 and games/0ad.
I'm assuming that this is no longer a problem since nobody has said anything to the contrary after comment #9.