CrossOver Support - Community Forums

After releasing Crosover 23.7 game still freezes sometimes and termination of Steam and CS2 are required. It is not deterministic. Sometimes I am able to play 2-3 maps without problem, sometimes game freezes and it is not responsive after couple of rounds. CPU utilization for Steam app goes over 100%.
I opened bug ticket for beta release: https://www.codeweavers.com/beta/crossover/browse?cmd=rpt_edit;report_id=22039

Devices:

Macbook Pro M1 Max 64 GB
Mouse Razer Abyssus Sampling 1000hz Resolution: 3500 dpi
Keyboard Corsair K70 Pro

Tested bottle settings:
DXVK enabled/disabled
D3DMetal enabled/disabled
ESync enabled/disabled
MSync enabled/disabled
High Resolution Mode disabled

Logs from CS2 console:
amNetSockets] Waited 2.3ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] Waited 2.4ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] Waited 2.2ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] Waited 2.6ms for SteamNetworkingSockets lock [GetSessionConnectionInfo]
[SteamNetSockets] Waited 2.1ms for SteamNetworkingSockets lock [GetSessionConnectionInfo]
[SteamNetSockets] Waited 2.3ms for SteamNetworkingSockets lock [GetSessionConnectionInfo]
[SteamNetSockets] SteamNetworkingSockets lock held for 5.5ms. (Performance warning.) ServiceThread,RecvUDPPacket(x2)
This is usually a symptom of a general performance problem such as thread starvation.
[SteamNetSockets] SteamNetworkingSockets lock held for 5.2ms. (Performance warning.) ServiceThread
This is usually a symptom of a general performance problem such as thread starvation.
[SteamNetSockets] Waited 2.0ms for SteamNetworkingSockets lock [GetSessionConnectionInfo]
[SteamNetSockets] Waited 2.1ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] Waited 2.1ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] SteamNetworkingSockets lock held for 5.2ms. (Performance warning.) ServiceThread,RecvUDPPacket(x2)
This is usually a symptom of a general performance problem such as thread starvation.
noname! connected
[SteamNetSockets] Waited 2.1ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] Waited 2.1ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] Waited 2.2ms for SteamNetworkingSockets lock [GetSessionConnectionInfo]
[SteamNetSockets] Waited 2.3ms for SteamNetworkingSockets lock [GetSessionConnectionInfo]
[SteamNetSockets] Waited 2.8ms for SteamNetworkingSockets lock [GetSessionConnectionInfo]
[SteamNetSockets] Waited 2.2ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] Waited 2.3ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] Waited 2.1ms for SteamNetworkingSockets lock [GetSessionConnectionInfo]
[SteamNetSockets] Waited 2.4ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] SteamNetworkingSockets lock held for 5.0ms. (Performance warning.) ServiceThread,RecvUDPPacket(x2)
This is usually a symptom of a general performance problem such as thread starvation.
[SteamNetSockets] Waited 3.1ms for SteamNetworkingSockets lock [GetSessionConnectionInfo]
[SteamNetSockets] Waited 2.4ms for SteamNetworkingSockets lock [GetSessionConnectionInfo]
[SteamNetSockets] Waited 2.4ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] SteamNetworkingSockets lock held for 5.3ms. (Performance warning.) ServiceThread,RecvUDPPacket(x2),SteamDatagramClientThinker::Think,EnsureDataCenterRoutesValid,ThinkPingProbes,ThinkSelectServer
This is usually a symptom of a general performance problem such as thread starvation.
[SteamNetSockets] SteamNetworkingSockets lock held for 5.0ms. (Performance warning.) ServiceThread,RecvUDPPacket(x2)
This is usually a symptom of a general performance problem such as thread starvation.
[SteamNetSockets] Waited 2.3ms for SteamNetworkingSockets lock [GetSessionConnectionInfo]
[SteamNetSockets] SteamNetworkingSockets lock held for 5.1ms. (Performance warning.) ServiceThread,RecvUDPPacket(x2)
This is usually a symptom of a general performance problem such as thread starvation.
[SteamNetSockets] Waited 2.5ms for SteamNetworkingSockets lock [SetConfigValue]
[SteamNetSockets] SteamNetworkingSockets lock held for 5.0ms. (Performance warning.) ServiceThread,RecvUDPPacket(x2)
This is usually a symptom of a general performance problem such as thread starvation.

It seems that adding -no-browser to Steam run options solves the issue.

You are right, I tried -no-browser on Mac M2 and CS2 works like a charm, no freezes... BUT, microphone doesn't work!
Even on Steam, when you try to test the microphone, no sound is detected. When i reopen Steam without -no-browser, mic works again.

Any thoughts?

Hi, unfortunately I wasn't able to solve issue with mic :/

Damn. I have the same problem. I'll eavesdrop, maybe someone will find a way out.

Hi guys! Facing this issue as well. CS2 completely freezes after several rounds (5-7). To get the game working it's needed to terminate the CS2 process (through Force Quit). After the process of re-launch and game re-join, most of the keys are not responding (movements, shooting), except for weapon changes (1,2,3,4)

Device info:
Macbook M1 Pro, 14"
Chip M1 Pro
MacOS Sonoma 14.1.2
Crossover 23.7

I reported this issue back in December 2023 and what Support replied to me:
Looking like there are some major outlying issues with this game that we are working on that should improve performance. Once D3DMetal is fully working for this game particularly, we shouldn't have any issues. Still continuously working on this game as we speak but do not have an estimate timeframe for when we will have a fix available

It seems -no-browser option is no longer needed if you use latest version of Crossover and D3DMetal + MSync. I haven't seen CS2 crashing since couple of weeks.

My observation: the issue is still in place, the game is crashing sometimes. But at least you can play the game after relaunching the process. -no-browser option applied

Setup:
Macbook M1 Pro, 14"
Chip M1 Pro
MacOS Sonoma 14.3.1
Crossover 23.7.1
D3DMetal + MSync

Markus_Holzer wrote:

My observation: the issue is still in place, the game is crashing sometimes. But at least you can play the game after relaunching the process. -no-browser option applied

Setup:
Macbook M1 Pro, 14"
Chip M1 Pro
MacOS Sonoma 14.3.1
Crossover 23.7.1
D3DMetal + MSync

Guys I think you're running into some placebo effect, -no-browser flag was discontinued back in early 2023. That flag was supposed to not start the web helper service, which saved resources for low-end pc gamers.
There are some workarounds to "kill it" after a few seconds, but the deamon in charge of keeping it open ramps up some CPU, so there is no real solution to this.

I'm still seeing freezes using D3DMetal with and without MSYnc on an M2 Max. I don't get freezes using Apple GamePortingToolkit 1.1.

Jonathan Doe wrote:

I'm still seeing freezes using D3DMetal with and without MSYnc on an M2 Max. I don't get freezes using Apple GamePortingToolkit 1.1.

I have the same Problem. Can you explain me exactly how you do that? Thank you!