Counter-Strike: Source Forum

This is a community forum and not official technical support. — If you need official support: Contact Us

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

What to do in a crash

hi!

i've solved a lot of problems and now i'm playing CSS regularly and it's great. thanks codeweavers!

however, occasionally i get a crash (which doesn't happen every single day, but frequently). i suppose it's only natural, because it's a windows vm. but what can i do in a crash? my mac is still responding (i can tell because the caps lock key lights up, and programs are still running on the background). i can't switch tasks from crossover because it locked out multitasking via cmd+tab, and the force quit shortcut doesn't work. i hate having to coldly kill my machine every time this happens. it's a mac! come'on!

help!

mike

Did you try option-command-r? (alt-apple-r)

yes, it does nothing

The things to try:

Command-Option-R to force CrossOver out of full-screen mode
Command-Q to quit CrossOver and any Windows program it's hosting
Command-Option-Esc to force quit CrossOver; this may put up a dialog behind the full-screen game; hit return to confirm the force quit operation

If none of the above works, then what you're experiencing is not a crash of the game but a lock-up of the Mac Window Server. The Window Server should not lock-up no matter what CrossOver does, but there are bugs in Apple's video drivers that cause it to. We don't really know why it's happening. If we did, we'd try to work around it.

If you have Remote Login enabled for your Mac (Sharing pane of System Preferences) and you have another computer nearby, you can use SSH to log into the Mac. Once there, it doesn't help to kill CrossOver or any of the Wine processes it creates. It doesn't even help to kill the Window Server process. The only thing you can really do is issue the "sudo reboot" command. That's at least a little better than forcibly powering the Mac down, as it gives the OS a chance to flush the file system.

ken, calling the force quit window and blidly pressing enter worked fine. thanks!

Well, I'm glad that that works for you. On the other hand, it's disturbing that none of the less drastic options work. 😥

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi02LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzMxNDM1MjAzLCJjc3JmX3Rva2VuIjoiV3NxZUNIZXZUYzNiRlRCUSIsImdkcHIiOjB9