Game freezes when you search for a beatmap in the carousel with the search bar
See original GitHub issueDescribe the bug: Not sure if it’s related to my large number of beatmaps in the carousel, but something has changed recently which seems to reduce performance when searching for a beatmap in the carousel with the search bar.
Screenshots or videos showing encountered issue:
- previous version:
2021.109.0
osu!lazer version: 2021.118.1
(The logs don’t seem to give any information about it)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Is there something wrong with beatmap listing's search bar?
Typing a song or keywords into the search bar is fine but actually trying to get the search request to go through is...
Read more >[resolved] Game freezes after beatmap is completed. - Osu! - ppy
When playing in online mode game randomly freezes (~every fifth songs on average) after beatmap is being completed and stats are shown.
Read more >osu! beatmaps crash the game :: Holodance Bug-Reports
On my monitor, the game window is frozen and it takes several clicks to ... On the osu songs (which are very new...
Read more >how to use search filters on osu! - YouTube
search filters have saved me years of my precious life, ... years of yours as well. less time finding maps and more time...
Read more >Opsu!(Beatmap player for Andro - Apps on Google Play
Opsu is an open-source version of osu! written in java and it is now on the play store. You can download beatmaps from...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Preliminary investigation shows that this was caused by the switch to .NET 5, and potentially a different pathway being used for
IndexOf
for better unicode support (presuming that’s what ICU stands for…?)https://github.com/dotnet/docs/issues/18423 https://github.com/dotnet/runtime/pull/34645
Code specifically:
https://github.com/dotnet/runtime/blob/69f260eff523bc16c8a95c232e4816b3a1764e88/src/libraries/System.Private.CoreLib/src/System/Globalization/CompareInfo.cs#L1117-L1120
This would imply that this has only ever been faster on windows (due to other platforms preferring ICU previously?). Still a cause for concern…
Further investigation: this is being tracked https://github.com/dotnet/runtime/issues/40942 (the most recent comment shows some improvements have been make for net 6.0) more specifically https://github.com/dotnet/runtime/issues/37815
It is feasible to disable ICU on windows to get back the performance short term, but probably not worth it? If anything, this says that we need to make this flow asynchronous in the future (which is something I already planned on visiting when switching this code across to realm).
Yes, I have noticed this. I suppose I should’ve changed my wording- I just wanted to see if this was still being addressed, and it seems to be. This is the one thing stopping me from switching to osu!lazer as my main client.
Thanks for everything ppy!