Cursor randomly freezes while playing.

[Jpe230]

Describe the bug
This bug rarely occurs (once a week), but when it does, it keeps freezing a couple of times, I have to restart the client and then everything would be fine.

Osu! seems to register the input just fine (look what happens when I failed the map).

I'm using Hawku's driver, and a Wacom CTL-480. The driver's console doesn't show any error and this bug hasn't been present in the Osu! Stable, so I personally don't think that my tablet's driver is the one to blame.

Steps to reproduce
None that I'm aware, it happens randomly.

Video of the bug
Link

osu!lazer version:
osu 2021.129.0.0

Logs:
Link

[bdach]

I would recommend starting out by removing the custom driver first anyway and seeing if it changes anything.

[peppy]

Yep, we can't deal with your request unless you test with normal drivers. Also, when it happens please confirm that your tablet is still providing input at a windows level. This doesn't look like something local to lazer.

[andrewhlu]

I had the same issue as well, where my mouse and keyboard would randomly stop working in game. Waiting about 5-7 seconds would allow the issue to resolve itself, and the inputs would work again as well. I think the issue occurred every 5-10 minutes when I was playing Kimi no Shiranai Monogatari -TV Edit- (Neoskylove) [Hard] nonstop for a few hours.

I'm not using a tablet though - I'm using keyboard + mouse. My mouse is the Logitech G203 Lightsync and my keyboard is the Corsair K68. Neither of those have custom drivers installed either - I am using the default drivers that came with both peripherals.

I unfortunately don't have a video of the bug. I can try screen recording the next time I play osu! so I can update this issue if it occurs again.

osu!lazer 2021.129.0, running on Windows 10 Education, build 19041.746

Logs are attached below:
runtime.log
updater.log
database.log
network.log
performance.log

[andrewhlu]

Ah figured I should add this:
While I don’t have a video to show (I played again for a few minutes but couldn’t repro), I can confirm that the behavior is the same as that of OP’s video (though you don’t need to pause the game for the issue to resolve itself). Also I remember seeing the Input Hz freeze at 1000 for a few seconds when it happened, then when it fixed itself, it would start counting up from a very small number until it got back to ~1000 and start updating at regular intervals again.

[peppy]

it would be very beneficial to see your frame graph when this happens, if you manage to capture it (ctrl+f11 twice). you may want to use something like window game capture where you can hit a hotkey to capture historical video, so you don't need to constantly capture until it happens.

[andrewhlu]

Gave it one more try before I went to bed... and I got it to reproduce. It actually crashed the game as well, which is a first.

10 seconds into the video, we can see the "Input" frame graph immediately freeze up (and behind it, you can see my keyboard buttons froze up as well). Just before the game crashes (around 20 seconds in), you can see the "Input" frame graph resume again, with some very low FPS values (94 FPS as opposed to the standard ~1000) and some very high latencies (almost 1 second)

Video:

osu-20210129-freeze.mp4

Logs:
network.log
performance.log
runtime.log
updater.log
database.log

[peppy]

That's about what I expected, thanks.

The next step would be to keep the performance overlay open when this happens (Ctrl+F2) and after it happens, there should be a performance.input.log with more useful information. We really need to determine what is causing the freezes on the input thread (my suspicions are on the game controller handling code) and this log will help us look into it further.

[Jpe230]

I'm not using a tablet though - I'm using keyboard + mouse. My mouse is the Logitech G203 Lightsync and my keyboard is the Corsair K68. Neither of those have custom drivers installed either - I am using the default drivers that came with both peripherals.

Interesting I'm using a Corsair K65 also with default drivers (iCUE), I'm going to swap keyboard, uninstall iCUE, and see if iCUE or my Corsair KB are the one to blame, since using default wacom drivers resulted in the same bug.

[andrewhlu]

I opened the overlay and reproduced the error a few times again, but I wasn't able to find a performance.input.log file after I closed the game. I do see performance-audio.log, performance-draw.log, and performance-update.log though, which I have uploaded below. Am I doing something incorrectly?

Video:
https://user-images.githubusercontent.com/34492835/106875304-60799480-668b-11eb-8de8-2a19110d52c3.mp4

Logs:
network.log
performance.log
performance-audio.log
performance-draw.log
performance-update.log
runtime.log
updater.log
database.log

[peppy]

Interesting. The log file likely wasn't created because it somehow didn't think there was a performance issue (will need to investigate further as to why). That said, from your frame graph I can 99% say that this is something else on your system blocking the (global) window message queue. I would start with the above lead you have (corsair software) and see if that helps at all.

[andrewhlu]

I unplugged my Corsair keyboard and switched to an Anne Pro 2 (using wired connection) and can confirm that the issue is still present. I still didn't get any performance-input.log file. I didn't uninstall the Corsair iCUE software though - maybe that's the reason why the issue is still occurring? I'll try uninstalling it to see if that changes anything.

I didn't get a video of it unfortunately. Not sure if the logs will help either, but I added them here anyway. (I think there's some issues with this beatmap, since I keep getting errors about accuracy circles / skinnables / drawables taking too long to load and blocking the thread).

Logs:
performance-update.log
runtime.log
updater.log
database.log
network.log
performance.log
performance-audio.log
performance-draw.log

[peppy]

Unplugging will not be enough. This is going to be triggered by software running on your PC (ie. something in your system tray, minimised, or running in the background). I'd recommend you shut down basically everything (using task manager if you need to) including the corsair processes running in the background and start from there.

[andrewhlu]

Okay, uninstalled the software, restarted my computer, and then immediately proceeded to open osu! and OBS again to try it out. Issue still occurs, and this time, it happened in the song select screen, not in game. Still no performance-input.log file. Confirmed one last time via Task Manager that iCUE software was not running (since it should have been deleted) before I submitted this comment.

Peripherals:
Anne Pro 2 (connected via wired USB connection)
Logitech G203 Lightsync

Video:
https://user-images.githubusercontent.com/34492835/106884128-c23efc00-6695-11eb-8008-d35434299cb8.mp4

Logs:
network.log
performance.log
performance-audio.log
performance-draw.log
performance-update.log
runtime.log
updater.log
database.log

[peppy]

Logs and videos won't help going forward unless you find the actual cause, so there's no need to post them again.

You may be able to find something from watching the task manager processes list (sorted by cpu) while reproducing the issue.