ppy / osu-stable-issues

Report critical osu-stable issues here
60 stars 11 forks source link

when watching a replay/someone or playing multi, doing alt+tab crashes the game #1033

Open catuhana opened 2 years ago

catuhana commented 2 years ago

This issue is happening to me for a long time actually, but when I ask to the other players if it happens to anyone, they say there's no such problem. So this is probably not reproducible by everyone, but it started to piss me off.

I couldn't find any crash log on osu!'s folder, but here's some Windows Event Viewer logs that I think may help. Also I'm leaving some PC info here since with compatibility mode or with playing my discrete GPU, its not crashing. So I think it might be a problem with my integrated GPU's driver's OpenGL thingy, but it looks like game uses OpenGL 2 so maybe its OpenTK's problem?

Also note that crash happens most of the time but not always at first plays, but after playing some. And game never crashes on compatibility mode.

Lastly, I found this topic at osu!'s forum, and their crash logs looks same with mine. But also their hardware is very different from mine.

Stack Trace
Application: osu!.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at OpenTK.Graphics.ES20.GL.CopyTexImage2D(OpenTK.Graphics.ES20.TextureTarget2d, Int32, OpenTK.Graphics.ES20.TextureCopyComponentCount, Int32, Int32, Int32, Int32, Int32)
   at #=z0lOhZiUVQcylMA$eDnweFTZqF6WS.#=zjoy75lE=()
   at #=z0lOhZiUVQcylMA$eDnweFTZqF6WS.#=zi0SUZboVtqwBLH3zug==()
   at #=zoDZCdgRwFXQ9k5LHv6_vBAM=.#=zJyIGxjg=(#=zpJHBB0k7vZEyWzJwHFXnI_w=, Boolean)
   at #=z0lOhZiUVQcylMA$eDnweFTZqF6WS.#=z0JrPgAs=(Boolean)
   at #=z0lOhZiUVQcylMA$eDnweFTZqF6WS.Dispose()
   at #=z_g8HYDo0ziBqo4ELwsr3fBpFUEQ0OnR9ZbFkM$AIV4of.  ​        ()
   at #=z1qEsnmR_NYnNu4eYE9Qf7zCt_1bP.#=zW00KwRTHNzaT()
   at #=zmGcBavNsjoYtDFRNGA==.#=zr6uFMYA=()
   at #=zMKEM2WWRDnkYd0UxtQ==.#=zVsraaEQTbII7(System.Object, System.EventArgs)
   at #=zGVaZmxVWUZ9kl9DHV3w2LIw=.#=z4levtsE=(System.Object, System.EventArgs)
   at #=zxGJ9G0QD4WT6Wxx$ZIvwyg0=.#=znGhSpsq3L1J5GSLlag==(System.Object, System.EventArgs)
   at System.Windows.Forms.Application+ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32)
   at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
   at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
   at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
   at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
   at #=zxGJ9G0QD4WT6Wxx$ZIvwyg0=.#=zXDvJyaA=()
   at #=zMKEM2WWRDnkYd0UxtQ==.#=zXDvJyaA=()
   at #=zMJd2osoR$SiQFk27fQ==.#=zy7IID0$j6T48(System.String, Boolean, Boolean)
   at #=zMJd2osoR$SiQFk27fQ==.#=zQkhiBWo=(System.String[])
   at #=zMJd2osoR$SiQFk27fQ==.#=zVP$WDJQ=()
   at #=zx4TeIY9tWkIIRoQJ5_7I_aKpqnqs.#=zyqoOYA0=()
Windows Application Error Fault Details
Faulting application name: osu!.exe, version: 1.3.3.7, time stamp: 0x630c419f
Faulting module name: ig4icd32.dll, version: 9.17.10.4459, time stamp: 0x573dfb62
Exception code: 0xc0000005
Fault offset: 0x000109ba
Faulting process ID: 0x26d8
Faulting application start time: 0x01d8c6ef0595c42b
Faulting application path: C:\Users\tuhana\AppData\Local\osu!\osu!.exe
Faulting module path: C:\Windows\system32\ig4icd32.dll
Report ID: 8f1cf443-7dd7-4757-8180-1873674e87f5
Faulting package full name: 
Faulting package-relative application ID:

GPU

catuhana commented 2 years ago

Windows Application Error Fault Details section shows Faulting module name and its one of my GPU's driver DLL, so its probably a driver problem. But I believe there's a workaround to fix it.

And very, very absurdly, the file that Faulting module path says doesn't even exists there, its on another path _(C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64e0797375598370d1).

smoogipoo commented 2 years ago

Are you running exclusive fullscreen? Does this happen in borderless? Are your GPU drivers up to date?

Based on the stacktrace, it looks like a nasty driver-level issue which may not be easy to work around.

catuhana commented 2 years ago

I don't have any option for exclusive for fullscreen (my laptop doesn't support exclusive fullscreen on lazer by the way, might be related), but maybe fullscreen mode with render at native option does it automatically? Here's a screenshot for available and activated screen settings. image

Game doesn't crash on borderless fullscreen mode, and I think it is expected.

Yes, my GPU drivers are up to date.

smoogipoo commented 2 years ago

my laptop doesn't support exclusive fullscreen on lazer by the way, might be related

The warning shows up incorrectly on Intel GPUs. It sounds like it is correctly running exclusive mode.

Do you know if this only started happening recently?

catuhana commented 2 years ago

No. It was happening since i started to play osu!, 2021 June.