1519702 - FF 64 does not show any tab. FF 63 works fine.

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[Klaus.Hachmeister]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0

Steps to reproduce:

update from FF 63.x to 64

Actual results:

Windows 10 (32 bits) latest updates installed
3.x GB RAM
Notebook
AMD Athlon II Dual-Core P320 CPU + ATI Mobility Radeon HD4200 graphics
After update to FF 64 it is impossible to show any tab.
no Internet-URL, no about:config, no load local file

but, automaticly update from 64.0 to 64.0.2 works
downgrade to FF 63 works fine

Expected results:

there is a new bug that results in malfunction on old 32 bit systems.
It is no bug in internet-connection (proxy or similar)
I dont think there is anything wrong with the firewallsettings
maybe buggy display output optimations ??

Comment 1

[Matthias Versen [:Matti]]

Can you please check if the safemode makes a difference :

• https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

and if that doesn't work, try a new, additional test profile:
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

but to be clear: you can load pages in the first tab but can not open additional tabs ?
I ask because you seem to have reported this bug with Firefox64

Comment 2

[Klaus.Hachmeister]

same problem in safe mode

I cannot load any pages. even on the first tab.

the "buggy" FF runs on a notebook from a friend.
My installation FF64 on my own notebook works fine.
This is what I use now.

Comment 3

[Klaus.Hachmeister]

There is a Windows 10 driver installed, but ..

Maybe the major problem is the old graphics card?

-> DirectX 10.1, Shader 4.0

Comment 4

[Matthias Versen [:Matti]]

Did you tested a new profile ?

Can you open about:support, select "copy text to clipboard" and paste it in notepad to a file and attach the file here using the "attach file" link in this report ?

The graphic card driver should not matter because the safemode also disable the hardware graphic acceleration in Firefox.

Comment 5

[Klaus.Hachmeister]

Attachment: requested about:support

Comment 6

[Klaus.Hachmeister]

Yes I uninstalled FF,
removed folder C:\Program Files\Mozilla Firefox,
removed folder %APPDATA%\Mozilla
reinstalled FF

With 64 no success,
with 63 everything fine, but I had to disable autoupdate in settings quickly.

I added about:support from FF63, because AFAIK all about:<anything> cannot be viewed on FF64

Comment 7

[Matthias Versen [:Matti]]

The only thing that I can see is that there is a third party Antivirus Software (Avast) installed but that should not create issues while loading Firefox internal about: pages

I can only propose that you try the mozregression tool.
That tool downloads Firefox builds that are generated each day and you can test them if they work or not.
The final result should show the change in Firefox that caused this problem.

• https://mozilla.github.io/mozregression/

2018-09-04 would be a good start date.

Comment 8

[Klaus.Hachmeister]

Avast plugin was installed on FF63 only.
I tried to disable Avast virus scanner with FF64, but no success.

Comment 9

[Cristian Craciun]

User Agent: Mozilla/5.0 (Windows NT 10.0; rv:64.0) Gecko/20100101 Firefox/64.0
Build ID: 20190108160530

I cannot confirm this issue considering I cannot reproduce it. I've tried to reproduce it using Windows 10 (x86) and by updating the 63 version to 64.

Could you please install the Beta version (v65) and the Nightly version (v66) to see if any of these version works for you?

I suggest to create a new profile for each version and activate the profile manager, you have the steps here: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager

Comment 10

[Sylvestre Ledru [:Sylvestre]]

Or can you try to uninstall avast ? (and then, install it again)

Comment 11

[Cristian Craciun]

Resolved as incomplete based on the fact that we can not reproduce this issue and we did not receive more info from the reporter.

If the issue still occurs please reopen this issue and provide us more info.