CrossOver Support - Community Forums

I have the promotional copy of Crossover 7 on my home Mac Mini, and all of the Windows applications I've installed on it so far have worked reasonably well (some cursor / mouse pointer problems on a drawing program, not too surprising).

Today I wanted to see if Crossover would support Altova's MapForce software in my job. So I installed Crossover 7 on my work MacBook Pro (2008 vintage), running Mac OS X 10.5.8 (exactly same as my 2006 vintage Mac Mini).

Starting Crossover 7 resulted in the intro pane and then an "endless" hang. I checked top (I'm a programmer), and the problem was that Crossover was burning about 50% CPU while endlessly allocating more memory to itself. It continued allocating memory space to the Crossover process until all 2GB of RAM was consumed, and it continued burning into 8GB of VM. At that point, I decided that it was clearly broken, and first tried stopping it with SIGTERM (ignored, continued running) and then SIGKILL, which did stop it.

Realizing that Crossover 7 was several years old, I downloaded the newest version on Codeweavers website, 10.1.1 and decided to test it in demo mode before buying it. I'm glad I did.

10.1.1 fails almost exactly the same way. I was able to start Crossover once, and run the MapForce installer, which appeared to work just fine.

Any subsequent efforts to run Crossover (by itself, not launching MapForce) or to run MapForce result in the same memory-eating failure.

Here's a snip from my system log. I'm not Mac OS X development expert (I do Unix/Linux/BSD, however), but this sure looks like a glaring failure on the part of Crossover to do something correctly:

[code]
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: Release Date: 18 December 2003
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: X Protocol Version 11, Revision 0, Release 6.8.2
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: Build Operating System: Mac OS X Apple Computer, Inc.
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: Current Operating System: Darwin obmbp-3.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: Before reporting problems, check http://www.codeweavers.com/support/
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: to make sure that you have the latest version.
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: XSERVTransmkdir: Owner of /tmp/.CrossOver should be set to root
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: Loading GLX bundle glxCGL.bundle (using Apple's OpenGL)
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: Display mode: Rootless Quartz -- Xplugin implementation
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: PseudoramiX screen 0 added: 1680x1029 @ (0,21).
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: PseudoramiX screen 0 placed at X11 coordinate (1440,0).
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: PseudoramiX screen 1 added: 1440x900 @ (-1440,80).
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: PseudoramiX screen 1 placed at X11 coordinate (0,59).
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: [DRI] screen 0 installation complete
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: Screen 0 added: 3120x1029 @ (-1440,21)
Jul 27 17:11:19 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: Screen 0 placed at X11 coordinate (0,0).
Jul 27 17:11:20 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: dyld: warning, DYLD setting caused circular dependency in /Users/chris/Desktop/CrossOver.app/Contents/SharedSupport/X11/lib/libGL.dylib
Jul 27 17:21:57 obmbp-3 [0x0-0x8d08d].com.codeweavers.CrossOver[947]: Quitting XDarwin...
Jul 27 17:22:19 obmbp-3 com.apple.launchd[73] ([0x0-0x90090].com.codeweavers.crossover CD helper[958]): Exited: Terminated
Jul 27 17:52:35 obmbp-3 com.apple.launchd[73] (0x10d790.Locum[1021]): Exited: Terminated
Jul 27 18:02:57 obmbp-3 com.apple.launchd[73] ([0x0-0x9f09f].com.codeweavers.CrossOver[1027]): Exited: Killed
Jul 27 18:03:53 obmbp-3 com.apple.launchd[73] (com.apple.coreservices.uiagent): Throttling respawn: Will start in 5 seconds
Jul 27 18:08:28 obmbp-3 com.apple.launchd[73] ([0x0-0xa50a5].com.codeweavers.crossover CD helper[1074]): Exited: Terminated
Jul 27 18:10:06 obmbp-3 com.apple.launchd[73] ([0x0-0xaa0aa].com.codeweavers.CrossOver[1191]): Exited: Killed
Jul 27 18:13:14 obmbp-3 com.apple.launchd[73] ([0x0-0xb20b2].com.codeweavers.CrossOver[1215]): Exited: Killed
Jul 27 18:16:18 obmbp-3 com.apple.launchd[73] ([0x0-0xb60b6].com.codeweavers.CrossOver[1229]): Exited: Killed
[code]

Since I have not purchased the product yet -- and at this point, darn glad I have not, since it fails out of the box -- I can't use the ticket system, hence this posting.

I'm local to the Twin Cities, and would be happy to bring my MacBook Pro over to the Codeweaver's office for demonstration / debugging, if that's of use to the Codeweaver development staff. I really like your product, and would like to buy and use it.

Sadly, Crossover Mac 11.2.0 on Snow Leopard 10.6.8 on a 4GB MacBook Pro from late 2008 fails very nearly the same way. Starting Crossover, it simply burns 100% of a CPU while allocating all RAM until it runs of VM memory.

Crossover Mac 10.x works just fine on my Mac Pro on Snow Leopard 10.6.8, so what gives?

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

Try completely resetting Crossover http://www.codeweavers.com/support/wiki/mac/mactutorial/uninstall and see if that helps the next time you launch it.

Thank you very much, Andrew. I did do an uninstall, but I must have missed some of the pieces. I followed instructions at the link you provided and then reinstalled, and version 11 now works on my MacBook Pro.