Alexandre Julliard
Alexandre Julliard
The lack of sound is suspicious, I'd look into that first. Also try WINEDEBUG=seh to see if the stack overflow is caused by an exception.
That looks suspicious, even if it's probably not the main cause. You can try looking for why there's no vectored handler set (through RtlAddVectoredExceptionHandler) in the failing case.
The equivalent would be `RtlCaptureStackBackTrace`, but you'd have to do the printing yourself.
> After some more debugging, I finaly noticed something strange: looks like BG3 used `GetLogicalProcessorInformation(...)` to gather cpu information (nothing special), but use Cache information to deduce the best number...