black box flashes screen when I am on navigation on firefox




3 years ago
3 years ago


(Reporter: gslima2016, Unassigned)


47 Branch

Firefox Tracking Flags

(Not tracked)



(1 attachment)



3 years ago
Created attachment 8768262 [details]
Captura de tela de 2016-07-05 22-11-27.png

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160606113944

Steps to reproduce:

I opened firefox and then at last I opened youtube. I thought I got hacked, as I thought It was a terminal session doing things. But that doesn't appear to be the case. but what is it?
PS. I removed cron and anacron packages because of security issues and I also disabled html5 videos.
Maybe a flash thing with firefox? I dont know.

Actual results:

This black box flashes the screen.

Expected results:

There should be actually nothing flashing on screen.


3 years ago
OS: Unspecified → Linux
Hardware: Unspecified → x86_64

Comment 1

3 years ago
Does it happen?

1) in safe mode:

2) with a fresh profile:
Flags: needinfo?(gslima2016)

Comment 2

3 years ago
1) It happens in safe mode.

2) It happens with a fresh profile, when I disable HTML5 Video, within a few videos playing.

Aditional info. When the black screen appears, appears the following error:

firefox -P
1467857564563	addons.xpi	WARN	Bootstrap state is invalid (missing add-ons: /home/cloacker6/.mozilla/firefox/pqbewsaz.gui/extensions/
Vector smash protection is enabled.

(process:20887): GLib-CRITICAL **: g_path_get_basename: assertion 'file_name != NULL' failed

The reason I am using flash instead of HTML5 Video is because html5 usually hangs and slows the system.
Flags: needinfo?(gslima2016)
Let's try Core :: Plug-ins because of the Flash usage.  Not clear yet if the bug is in Firefox or Flash itself.
Component: Untriaged → Plug-ins
Product: Firefox → Core

Comment 4

3 years ago
This will likely be fixed when we force Flash to be windowless, but until then we don't have the engineering resources to investigate this.
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.