Momentary blue screen with diagonal lines starting ff18




6 years ago
6 years ago


(Reporter: pcb1970, Unassigned)


18 Branch
Windows Vista

Firefox Tracking Flags

(Not tracked)



(2 attachments)



6 years ago
Created attachment 700685 [details]

User Agent: Mozilla/5.0 (Windows NT 6.0; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20130104151925

Steps to reproduce:

ff updated automatically from ff17 to 18. 

Actual results:

After the update, starting the browser caused this momentary blue background screen with diagonal lines. See attachment. This then disappeared when the webpage loaded. This has never happened on any version of ff I have had. 

Expected results:

No annoying blue flash.

Comment 1

6 years ago
Reverting to ff17 cures the problem.
Please try this:

a) start Firefox in the Firefox safemode:
b) in case that it works in the safemode disable the hardware graphic acceleration in tools/options/advanced/general (FF restart required)
c) if that fixes your issue please post the graphic section (not everything) from about:support

Comment 3

6 years ago
Safe mode and disabling hardware acceleration did not work. Although, the duration of the blue flash was shorter. Reverted back to ff17.
We have no other reports about this issue and I don't know why it happens on your system after you disabled everything with running Firefox in the Firefox safemode.

Comment 5

6 years ago
Created attachment 701439 [details]
Wordweb addon has a conflict with ff18

conflict with ff18

Comment 6

6 years ago
Sorry, I misunderstood. I did them separately. Doing them together seems to have eliminated it. I left hardware acceleration off and tried disabling addons one at a time. Wordweb, an online dictionary addon, seems to be the culprit.

Comment 7

6 years ago
Just turned hardware acceleration on again and the blue lines come back! I'll leave it off and disable wordweb. And keep ff18.
As for comment 6 it seems that the origin is due to the addon Wordweb and not a Firefox problem.
I'll close this as INVALID.
Last Resolved: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.