Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Firefox won't redraw on analog monitor driven by Radeon 4350 graphics card

  • 1 Antwort
  • 1 hat dieses Problem
  • 7 Aufrufe
  • Letzte Antwort von guigs

more options

I'm running two XP SP3 on a reasonably current desktop with 4 GB and an ASUS Radeon 4350 graphics card with 512MB. The card drives two Samsung SyncMaster 2443 monitors, one from analog RGB port, the other from a DVI port. I've been using Firefox since v.3, but sometime around v.8 or v.9, it began to have problems when ever I had a Firefox window open on the analog video port. (I'm current with v.27.0.1)

The window 'appeared' to freeze - clicks, scrolling and the like failed to produce a re-drawing of the window's content. However, if I dragged the window over to the other monitor running off the DVI port, the Firefox window would re-draw itself with the new content. This behaviour told me two things. On the analog port the Firefox window was still alive, and responding to keyboard and mouse inputs, but not displaying the results. Secondly, the problem was related to the Firefox - RGB interface. Oh! I forgot to mention: Firefox was the only application exhibiting this behaviour.

A support session with ASUS produced no solution. After searching several related Mozilla support issues, on a problem closely related to mine someone suggested turning off the hardware accelerator, and re-starting Firefox (Tools > Options > Advanced > General > "Use hardware acceleration when available"), which I did. Poof! Problem solved, case closed. Except, Why?

Is this just because of my hardware setup? Or Firefox - I generally have 6 to 10 windows open at a time, some with several dozen tabs (I'm a software architect, so tend to keep a lot of context on the desktop). I'm glad I can scroll Firefox now on my other monitor, and click buttons and be able to read the response, but I think there's a defect here somewhere...

I'm running two XP SP3 on a reasonably current desktop with 4 GB and an ASUS Radeon 4350 graphics card with 512MB. The card drives two Samsung SyncMaster 2443 monitors, one from analog RGB port, the other from a DVI port. I've been using Firefox since v.3, but sometime around v.8 or v.9, it began to have problems when ever I had a Firefox window open on the analog video port. (I'm current with v.27.0.1) The window 'appeared' to freeze - clicks, scrolling and the like failed to produce a re-drawing of the window's content. However, if I dragged the window over to the other monitor running off the DVI port, the Firefox window would re-draw itself with the new content. This behaviour told me two things. On the analog port the Firefox window was still alive, and responding to keyboard and mouse inputs, but not displaying the results. Secondly, the problem was related to the Firefox - RGB interface. Oh! I forgot to mention: Firefox was the only application exhibiting this behaviour. A support session with ASUS produced no solution. After searching several related Mozilla support issues, on a problem closely related to mine someone suggested turning off the hardware accelerator, and re-starting Firefox (Tools > Options > Advanced > General > "Use hardware acceleration when available"), which I did. Poof! Problem solved, case closed. Except, Why? Is this just because of my hardware setup? Or Firefox - I generally have 6 to 10 windows open at a time, some with several dozen tabs (I'm a software architect, so tend to keep a lot of context on the desktop). I'm glad I can scroll Firefox now on my other monitor, and click buttons and be able to read the response, but I think there's a defect here somewhere...

Alle Antworten (1)

more options

I think it has something to do with the acceleration compatibility of many type of graphics cards.

"Unfortunately, due to the wide range of possible driver, video card and operating system combinations, hardware acceleration or 3D web graphics (WebGL) may still not work for you in Firefox. In these instances you fix the problems by disabling hardware acceleration and WebGL. " Ref https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardwar...