Try to disable hardware acceleration in Firefox.

• Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
• https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

• https://hacks.mozilla.org/2010/09/hardware-acceleration/

Yep, that fixed it. Thanks! But I shouldn't have to do this. Hopefully it will be fixed in the next RC. Thanks again.

Chris

You're welcome.

I have deployed Firefox to about 30 company computers and they are all set up with the Mozilla Update Service. When these computers automatically update to 16.0.1, I will have to go around to each computer and fix every single one. Please please fix this next release and save me this headache.

You can disable hardware acceleration via a mozilla.cfg file in the Firefox program folder.

• C:\Program Files\Mozilla Firefox\
• C:\Program Files (x86)\Mozilla Firefox\

You can do that with pref() or lockPref()
You can set these prefs as a start and add others if you need to initialize those as well.

pref("layers.accelerate-all", false);
pref("layers.acceleration.disabled", true);

Use a mozilla.cfg file in the Firefox program folder to lock prefs or specify new (default) values.

Place a file local-settings.js in the defaults\pref folder where you also find the file channel-prefs.js to specify using mozilla.cfg.

pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0); // use this to disable the byte-shift

See:

• http://kb.mozillazine.org/Locking_preferences

You can use these functions in mozilla.cfg:

defaultPref();  // set new default value
pref();         // set pref, but allow changes in current session
lockPref();     // lock pref, disallow changes

You are missing the point. As a system administrator, I installed Firefox company-wide with Mozilla Maintenance Service turned on. That means Firefox is automatically updated. If Mozilla releases a new version that breaks everyone's Firefox in my company, and I am forced to go around to EVERY computer and apply the fix, then I might just go Chrome this time, so I don't get burned again.

What good is Mozilla Maintenance Service if I can't trust Mozilla to release automatic updates that won't render my company's browsers inoperable?