CrossOver Support - Community Forums

I'm using the current trial version (signed up & downloaded yesterday) on a 2008 Macbook Pro with Nvidia graphics card and MacOS X 10.6.7

The freshly installed Crossover games starts without problems. Then I install a game, the installation runs through successfully, typically to the point where the game launches, as expected. Then I quit crossover games and all running applications. The next time I try to start crossover games, the program becomes unresponsive and starts using up a large amount of memory. Eventually, after 5-10 minutes, it crashes. Not that I do not even get to try and start any installed software. Here is a part of the crash report that might be relevant:

9   com.codeweavers.CrossOverGames    0x00041b24 -[CXServerCrossOver addMenusForDir:toMenu:skippingFileNumbers:] + 61
10  com.codeweavers.CrossOverGames    0x00041e36 -[CXServerCrossOver addMenusForDir:toMenu:skippingFileNumbers:] + 847
11  com.codeweavers.CrossOverGames    0x00041e36 -[CXServerCrossOver addMenusForDir:toMenu:skippingFileNumbers:] + 847

Fix: If I kill crossover games, and remove the "Bottles" folder, crossover games starts normally again.

Games tried:

Rift, using the existing windows/bootcamp installation
Rift, using a fresh install from DVD (install goes through, though slower than on windows)
Perpetuum, using the CrossTie

For each new attempt I removed the previous Crossover games installation as well as the Bottles folder.

Note: The game installation themselves are not a problem. I was able to play both Rift and Perpetuum after copying the bottle that crossover games created, and starting them using PlayOnMac (another Wine build for macs).

Did anyone experience something similar? Any ideas for a fix?

This issue has been forwarded to the Official CodeWeavers Ticket System. If you have observed this issue and would like to report it as well, please open a support ticket or send an email to info@codeweavers.com with a description of what you are seeing and a link to this post.

Thank you!
The CodeWeavers Team

Support helped me fix the problem. Thanks.