After updating to 2019.930.0, osu!lazer begins to freeze again. Just like what happened to previous issue, it could be related to Xamarin.
Current State: _Somewhat freezes in latest release (2020.215.0)._
Images:


Can confirm, this has been happening throughout the day for me
iPad Pro 11” running iPadOS 13.1.2 public stable release
Can replicate on the testflight build, but I can't seem to replicate this on a local debug build (netcore 3.0 sdk / mono 6.0.0)
As per last time, will update the build chain and see how that copes. More importantly than .net core or mono version is xamarin.ios version (@smoogipoo please include what you tested for reference).
Also if trying to repro you should be on release, not debug. Optimisations matter a lot in these cases.
Xamarin.iOS
Version: 12.14.0.114 (Visual Studio Community)
Seems like a fairly old build, I'll try to test again after update.
Still occurs in latest version 2019.1011.0.
Yes, we are aware it is not fixed yet. This requires debugging and likely error submission to Xamarin.
Latest git causes my iPhone XS to crash, can't check iOS version, as I can't bypass the app. Can't shutdown the system, idk why, the power slider won't display. Am stuck with a completely black screen.
Please google instructions on rebooting your phone.
When sidebutton+volume up (or down) doesn’t react, and that’s the only thing google instructs, then there’s really not much to do besides waiting and hoping.
On 28 Nov 2019, at 14.21, Dean Herbert notifications@github.com wrote:
Please google instructions on rebooting your phone.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/ppy/osu/issues/6355?email_source=notifications&email_token=ABWI7E7TWTTOJJI66YD5LETQV7AT5A5CNFSM4I4NRJN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFMS2UY#issuecomment-559492435, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABWI7E6U7KPBPYGM576HDDDQV7AT5ANCNFSM4I4NRJNQ.
Took me exactly one Google search:
https://www.macrumors.com/how-to/force-restart-iphone-11-iphone-11-pro-max/
Same process applies to iPhone XS.
Didn't see the section to force turn off the phone. Doesn't change the fact that Osu!Lazer soft-bricked (for a lack of better term) my phone, and I'd like to know how to troubleshoot why, so I can help fix this issue!
You will need to debug and investigate.
Not sure about others, but lazer 2019.1213.0 hasn’t frozen once for me today.
I take back my statement, freezes are much less often though.
I take back my statement, freezes are much less often though.
@ThatsNiceGuy
It will still occur if you keep on playing longer in the app when playing multiple beatmaps. I’m still waiting for 2 months to get the fix as much as you do.
Now is very often on iOS and due to the new TestFlight link I can’t rollback to a version to where it didn’t happen.
Lazer 2019.1219.0
Now is very often on iOS and due to the new TestFlight link I can’t rollback to a version to where it didn’t happen. ...
@ThatsNiceGuy did you mean previous versions before chaotic actions caused by Xamarin.iOS? I’ve been experiencing this when this bug is reintroduced and is still there up until _latest_.
Yes, by “previous versions” I mean builds before October. I had been using a build from September so it wouldn’t crash all the time
There was a suggestion made at #7375 about how this might occur when break time starts - can anyone else confirm if that's the particular scenario freezes occur at, or are they essentially random?
It also occurs randomly too sometimes for me, but for the most part if I ever get freezes it’s on certain beat maps that I play
it seems to occur randomly for me but more when the game is doing something that would stress the system like huge concentrations of notes and stuff like that
I believe this is going to be GC related. I had a similar issue with another iOS project under xamarin and it turned out to be incorrect freeing or native memory.
Next step would be reproducing with debug available.
Closing as this has been resolved in latest February builds.
Awesome!
Sorry to be a bearer of bad news but this still happens on the osu! ruleset (not mania, taiko or ctb) on the latest 2020.215.0 release on TestFlight.
Device: iPhone XR 128GB
osu!supporter TestFlight link
Can you reliably reproduce? Specific beatmap? How long until reproduction?
Sorry to be a bearer of bad news but this still happens on the osu! ruleset (not mania, taiko or ctb) on the latest 2020.215.0 release on TestFlight. ...
@ThatsNiceGuy - weird, I’ve been running this game for 30 minutes without any issues whatsoever...
Yeah it still happens aswell to me running on iPhone 8 Plus 64GB. Used TestFlight link.
It just happens out of the random most of the time. Never happens on taiko, mania, or ctb
Earlier today I got it to freeze on this map:
https://osu.ppy.sh/beatmapsets/122390#osu/313050
on Lunatic difficulty with storyboard off.
Happened upon tapping the first note of the song.
As the person above me said, it seemingly happens at random (no storyboard should be fine, memory usage wise) but it does happen consistently when the game is running out of memory on osu!standard maps with storyboard enabled. I never get any freezes in mania, ctb or taiko.
It freezes for me on that map too. For me it loves to freeze on break times for basically all beatmap
I'm able to replicate this and will take a quick look into it.
Investigated this a bit further and this is the best I could come up with: https://github.com/mono/mono/issues/18925
Seems to be a low-level mono issue as far as I can tell.
The problem seems to happen occasionally on Android devices.
The problem seems to happen occasionally on Android devices. ...
@ojh050118
Can you confirm this also occurs in your device?
Further discussions on the issue: https://github.com/mono/mono/issues/18973
Can confirm this still happens on both of my iOS devices (iPad 7th gen 128gb) and (iPhone XS Max 64gb)
_Just wanted to let you know :)_
Nice! I can test on some devices when this commit is included in a build submitted to TestFlight
Most helpful comment
I believe this is going to be GC related. I had a similar issue with another iOS project under xamarin and it turned out to be incorrect freeing or native memory.
Next step would be reproducing with debug available.