NelloKudo
osu! crash when exiting a song or passing a map
im using zorin os and sometimes the game just freezes with a black screen when i exit a song or pass a map it says osu!.exe is not responding and i can force quit the game this issue didnt happen to me on other distros
0024:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x200 for device 0.
0318:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
030c:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
030c:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
0024:fixme:crypt:SystemFunction041 (08EA8784, 10, 0): stub [RtlDecryptMemory]
0024:fixme:crypt:SystemFunction040 (08EA8784, 10, 0): stub [RtlEncryptMemory]
031c:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
0370:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
0024:fixme:crypt:SystemFunction041 (08EA8784, 10, 0): stub [RtlDecryptMemory]
0024:fixme:crypt:SystemFunction040 (08EA8784, 10, 0): stub [RtlEncryptMemory]
036c:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
0024:fixme:crypt:SystemFunction041 (08EA8784, 10, 0): stub [RtlDecryptMemory]
0024:fixme:crypt:SystemFunction040 (08EA8784, 10, 0): stub [RtlEncryptMemory]
0398:err:sync:RtlpWaitForCriticalSection section 0035E308 (null) wait timed out in thread 0398, blocked by 0024, retrying (60 sec)
/home/jeydin/.local/bin/osu-wine: line 66: 367755 Killed $LAUNCH_ARGS wine "$OSUPATH/osu!.exe"
I'm not sure what the top lines mean but when I finish a map it freezes the screen and then it says the Osu isn't responding. This only happens occasionally though, it's kind of random
https://github.com/NelloKudo/osu-winello/assets/62669147/144aac3b-5f24-4504-a468-cde0753a368c
Don't mind my accuracy :sob: It was so bad I crashed Osu :sob: :sob: :sob:
yeah like the video i had the same problem, seems like its an issue on ubuntu/ubuntu based distros?
On Mon, Apr 8, 2024, 5:16 AM Jeydin21 @.***> wrote:
https://github.com/NelloKudo/osu-winello/assets/62669147/144aac3b-5f24-4504-a468-cde0753a368c Don't mind my accuracy 😭
— Reply to this email directly, view it on GitHub https://github.com/NelloKudo/osu-winello/issues/65#issuecomment-2041788358, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHOCX3WWOQ32M7UQ67QEAMLY4IDZNAVCNFSM6AAAAABE2OVRUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBRG44DQMZVHA . You are receiving this because you authored the thread.Message ID: @.***>
2024-04-07.22-12-55.mp4
Don't mind my accuracy 😭 It was so bad I crashed Osu 😭 😭 😭
Kinda unrelated to the issue, but are you sure your drivers are installed properly? 17ms is waaay too much :/ Check the drivers page in the repo and run the commands again or try changing kernel!!
Since logs seem to fail in sync, I wonder if fsync is the culprit here…
Run osu-wine --update to make sure you’re on the latest Wine version and, if that doesn’t help, follow this (the fsync part!!)
Then can you try editing ~/.local/bin/osu-wine and commenting out (or deleting) WINE_BLOCK_GET_VERSION=1?
It happens to me too, in this script and in lutris, I have no solution so far ): (I also use Zorin OS)
Hello farmers, I come here with a possible fix which worked on my fresh installation of Debian using i3wm.
Before I was showing similar issues, the game would freeze up whenever submitting scores, exiting a beat map, or even just randomly while f2'ing in the song select about every 10 minutes. I have been bashing my head at this for a bit and have been able to play for an hour now without any crashes, and on-going. I will edit this if any crashes occur in the future.
List of modifications
Mainly, the two changes I made which made the crashing stop was the following:
# 1. Installing winbind as it was an err from wine output
sudo apt update
sudo apt install winbind
# 2. Open winecfg from osu-wine
./osu-wine --winecfg
# Go to the Staging tab and uncheck "Enable CSMT for better graphic preformance"
Some other changes I made while debugging which may be related is the following:
- In osu!stable, change your "Release stream" in settings to "Cutting edge (Experimental)".
- In winecfg, change your Windows Version to Windows XP 64
- In the osu-wine script, comment out the following lines:
#export WINEESYNC=1 # Enables esync (when possible)
#export WINEFSYNC=1 # Enables fsync (when possible)
^ To be honest, I'm not quite sure what this does and if its good, but performance hasn't been impacted by commenting this out.
Unrelated quality of life
This is unrelated but worth noting to anyone reading. While using a compositor such as picom/compton my latency is around 10ms, after killing the picom process my latency in osu! hovers around 0.9-1.5ms, this might be valuable to anyone who is experiencing high latency on Debian based distributions.
@LixxRarin @risexd1 @Jeydin21 Are any of you able to confirm if this works on your end?
Sorry for the delayed response, I will try this when I wake up tomorrow 😄
I've switched to an arch linux based-distribution (which is working normally), but I'd like to test that out if I can :D
It was working perfectly fine for about 3 hours, then I decided to start streaming because I was feeling confident. It ended up crashing within 5 minutes of starting the stream, very strange. I'm not quite sure anymore...
I also freeze / crash with the same error similar to:
0398:err:sync:RtlpWaitForCriticalSection section 0035E308 (null) wait timed out in thread 0398, blocked by 0024, retrying (60 sec)
Though I would like to revive discussion / investigation into this if any of you have the free time. There is a plenty of Debian users who are using lazer right now because of this.
It was working perfectly fine for about 3 hours, then I decided to start streaming because I was feeling confident. It ended up crashing within 5 minutes of starting the stream, very strange. I'm not quite sure anymore...
I also freeze / crash with the same error similar to:
0398:err:sync:RtlpWaitForCriticalSection section 0035E308 (null) wait timed out in thread 0398, blocked by 0024, retrying (60 sec)Though I would like to revive discussion / investigation into this if any of you have the free time. There is a plenty of Debian users who are using lazer right now because of this.
I’ll get a fresh install of Debian and try myself for a bit as well. Really strange issue as it only occurs on Debian/Ubuntu based distros ://
Unrelated but regarding your QoL advices above, yeah compositor turned off is a must on X11, but if you use Picom (which many do on i3) setting unredir-if-possible=true; in Picom’s config does the same job ;)
~If you're having this issue and want to test a new winello release before it's finalized, here is a prerelease binary: https://github.com/whrvt/WineBuilder/releases/tag/9.11-2~
It's not guaranteed to fix the hanging/crashing issue, but it should generally be an improvement over the previous version. ~Until it's merged, you will have to copy the files from the archive to overwrite your old installation manually.~
Related PR: https://github.com/NelloKudo/WineBuilder/pull/2
~If you're having this issue and want to test a new winello release before it's finalized, here is a prerelease binary: https://github.com/whrvt/WineBuilder/releases/tag/9.11-2~
It's not guaranteed to fix the hanging/crashing issue, but it should generally be an improvement over the previous version. ~Until it's merged, you will have to copy the files from the archive to overwrite your old installation manually.~
Related PR: NelloKudo/WineBuilder#2
I can confirm crash is still happening with this PR on Debian. Works out of the box on Arch based distros.