Unable to login - invalid pointer address

[tsbreuer]

Type

Game behaviour

Bug description

I'm not completly sure. A full recollection of incidents is as follows.

On the morning i figured i needed to turn on hyper-v again for a future work-related necessity so i did, but i wasnt able to reboot the system at the time, since the need for hyper-v wasnt inmmediate, i just figured i'd postpone the reboot.

Later during the day i installed osu!Lazer. It worked fine and everything, and i was able to login. As i was playing after a long time, i dusted off the wacom tablet i had and went and grabbed the hawku drivers (I didnt know at the time lazer had already tablet support integrated), and as part of the install, reboot was necessary.

However, unknown to me was that for whatever reason, there's some issue with windows that makes enabling hyper-v cause a bootloop. The fix was a system rollback/restore. However, that also uninstalled lazer. Fine i guess.

However, after reinstalling lazer i'm now unable to login, with the error "The system detected an invalid pointer address in attempting to use a pointer argument in a call" pops up and login fails.

Screenshots or videos

Version

2024.412.1-lazer

Logs

logs.zip

[smoogipoo]

Looks like you've broken your networking in the rollback.

Running this may fix it for you:

netsh winsock reset

[tsbreuer]

It was indeed what fixed it. Would it be possible that the error be included in the error message in a more descriptive way or at least in a FAQ anywhere? googling the error brought up no info whatsoever.

Well at least now this discussion pops up in google if you add "osu!" at the end of it

[peppy]

Do keep in mind, you're the first out of hundreds of thousands (if not millions) that have played lazer to hit this.

[smoogipoo]

Fwiw this is where the fix originally came from: https://stackoverflow.com/questions/19011876/net-mysql-connection-fail-the-system-detected-an-invalid-pointer-address-in Obviously to get to this requires some very specific search terms.

This is the second time I've seen it from one of our users, both cases as a result of user misconfiguration, so we don't need to change anything or add a FAQ at this point, as hinted towards above.

[smoogipoo]

As a side question: are you using IPv6? It may be one of those things that gets "fixed" (in that the misconfiguration is silently bypassed) when/if .NET ever gets happy eyeballs (dotnet/runtime#26177).

[tsbreuer]

Nope, not usig IPv6.