Susume Lv 1
Maybe some or all of the openAL exceptions in the various log files are a red herring. Maybe openAL throws exceptions all the time but does not crash the client. Then some other error crashes the client, and when the error handler looks up what the last error was, the new error has not left data in the error stack and the most recent data is left over from the latest openAL error, so that gets reported in the log.
Or maybe the client is trying to look up the appropriate sound for the latest event, but the latest event is an error, and passing that to the openAL lookup function crashes openAL.
In the former case, disabling openAL will change what gets reported to the log (possibly to no report, or possibly to some other red herring) but will not remove whatever error is actually crashing the client. In the latter case, disabling openAL may reduce the crashing, or may change what is reported to the log (as the original error might be reported), or both.
