Avatar for Username

ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefox 16.02 hardware acceleration osx imac started causing screen corruption

  • 2 (ردّان اثنان)
  • 2 have this problem
  • 6 views
  • آخر ردّ كتبه imatsig

imatsig
imatsig
more options

Weird screen corruption with Firefox 16.02 with hardware acceleration switched on. iMac 11,1 Intel Core i7 2.8 GHz running OSX 10.6.8 with ATI Radeon HD 4850 display hardware.

Some bizarre effects like a surround on two sides (top and right) of main Firefox window with elements captured from the top and side of main screen which on occasions flash at high speed and also a mouse focal point offset

I've tried Firefox safe mode and extensions plugins disabled and it definitely seems to be caused by switching hardware acceleration on as problems disappear when switched off.

Never had this problem before in several years use of Firefox until 16.02

Weird screen corruption with Firefox 16.02 with hardware acceleration switched on. iMac 11,1 Intel Core i7 2.8 GHz running OSX 10.6.8 with ATI Radeon HD 4850 display hardware. Some bizarre effects like a surround on two sides (top and right) of main Firefox window with elements captured from the top and side of main screen which on occasions flash at high speed and also a mouse focal point offset I've tried Firefox safe mode and extensions plugins disabled and it definitely seems to be caused by switching hardware acceleration on as problems disappear when switched off. Never had this problem before in several years use of Firefox until 16.02

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

If hardware acceleration in Firefox isn't working properly then you will have to leave it disabled.

imatsig
imatsig صاحب السؤال
more options

Thanks for the link. Has something changed in FF v16.02 hardware acceleration that you are aware of that might have caused this?