500956 - Running Crossover applications causes Firefox to become unresponsive (Mac)

Status: NEW

(Firefox :: General, defect)

Description

[Caspy7]

This applies to Firefox 3.5 RC3 on the Mac.

When I run an application in Crossover, Firefox becomes unresponsive for a few minutes and then responsive again for a few seconds and then back to unresponsive again (and so on so forth).  When it's unresponsive the cursor generally becomes a spinning beach ball.  This makes the application basically unusable even though it has not crashed.

In Activity Monitor, Firefox shows as not responsive, but curiously it's CPU usage drops to virtually zero.  Also, either the Crossover program (not the Crossover Application itself) or 'Wineloader' will show up in Activity Monitor as unresponsive.  Once I close or kill the windows program, Firefox begins running properly.

If I am running the Crossover Application alone, but no windows programs in it, this problem does not occur.
I have tested this with IE in a windows 98 bottle, IE in a win2k bottle and a program I use called TNTMpd in a windows 98 bottle.  All of these predictably made Firefox unresponsive only while they were running.

If this is reliably repeatable on other computers, that means no one who wants to run a Crossover application can also run Firefox.  I'd consider that to be a pretty significant bug.

Comment 1

[Caspy7]

Forgot to mention: Crossover version 7.1.0

Comment 2

[Mike Beltzner [:beltzner, not reading bugmail]]

Is this a regression? I don't think we'll block the final release of Firefox 3.5 on a compatibility issue with a third-party application, especially when we don't know what Crossover is doing (nobody here runs with it) but I'm interested in understanding the problem so we can try to fix it in a future stability release.

Comment 3

[Caspy7]

Note, for those wanting to test this out.  If you don't have Crossover installed, you can get a 30 day demo here: http://www.codeweavers.com/products/cxmac/download_trial/