loukingjr wrote:which Mac or Macs are you running OSX 10.6.8 or OSX 10.9 on?
snow leopard: 17" MacBook Pro (2009)
mavericks: 11" MacBook Air (2013)
from what you said the only set up you are having issues with is the MacBook running 10.6.8 and a Centos guest? post the vbox.log(compressed) for your Centos guest.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
loukingjr wrote:
from what you said the only set up you are having issues with is the MacBook running 10.6.8 and a Centos guest? post the vbox.log(compressed) for your Centos guest.
yes, it's only my old MacBook Pro, and only with the newest updates of centos for firefox. Now I'm using an older version (firefox-24.4.0-1.el6.centos) without issues. I can post the vbox.log at sunday at the earliest.
well, ff30 has a bigger memory footprint for one thing, I don't know how close you are to filling the guests memory. As I mentioned, I would try starting Firefox 30 in safe mode. Will look for a post on Sunday or so.
OSX, Linux and Windows Hosts & Guests
There are three groups of people. Those that can count and those that can't.
loukingjr wrote:well, ff30 has a bigger memory footprint for one thing, I don't know how close you are to filling the guests memory. As I mentioned, I would try starting Firefox 30 in safe mode. Will look for a post on Sunday or so.
here you find the log files, one for firefox-24.4 and two for firefox-24.6 (one with firefox started in secure-mode). May be you can't find an issue in the logs, after updating firefox from 24.4 to 24.6 the problems seemed to be gone.
loukingjr wrote:you could try turning off hardware acceleration for the problematic FF. It's in preferences>general.
with firefox-24.4.0-1.el6.centos.x86_64 there is no problem, only the newer updates produce the graphics corruptions
I have VBox 4.3.26 on Windows 7 with a Linux guest running Fedora 20 and Firefox 37.0.1 and I have the same issue.
It also crashes with SeaMonkey. I turn of 3d acceleration in the vbox setup and the problem goes away. Disabling it in Firefox doesn't help.