Closed Bug 1577247 Opened 5 years ago Closed 5 years ago

Page goes blank when downloading

Categories

(Core :: Graphics: WebRender, defect, P3)

70 Branch
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: thanatos.sith, Unassigned)

References

Details

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

Steps to reproduce:

Download a file.
Exemple :
goto https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2019-06/R/eclipse-cpp-2019-06-R-win32-x86_64.zip
Download the Windows 64 bits.

Actual results:

The page is redirected and loads up and the download dialog shows up.
Immediately after, the webpage goes blank.
The address bar sometimes still shows the url, sometimes not.
If the URL is present, after copying it to the clipboard, pasted it, the text is "about:blank".
Change tab return to this tab, the URL is gone.
Impossible to use the previous page function.
It happens on other websites since a few days/week in Nightly.

Expected results:

File start downloading and webpage does not disappear.

Hey thanatos.sith,

Can you please retry those sites using a new clean profile or disable addons?
Is this issue reproducible only on Nightly or on other versions as well?

Couldn't reproduce the issue using the steps provided on Windows 10 x64, latest Nightly.

Here are instructions for the new profile and Safe mode (add-ons disabled):
Safe mode: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode.
New Clean Profile: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Flags: needinfo?(thanatos.sith)

Hey,

I had it in safe mode but not with today's build using mozregression.

I refreshed my profile and synced it up and it now the bug is gone =) Should have tried this before reporting. Sorry.

Flags: needinfo?(thanatos.sith)

Okay so I did some more testing.

I have this bug when WebRender is ON.

I changed my GPU some days ago, so maybe it is related to the driver.
I was using the embedded (in W10) legacy driver for AMD (Radeon 5870).
Now i am using the latest 19.8.1 AMD driver.

I also have two bugs when WebRender is ON which appeared at the same time than this one.

Do a google search. Ctrl+click on a result link. The "go backward" button is active and if you press it reloads the google proxy URL to the actual result webpage. This does not happen without webrender.

Also if I scroll down on the same google result page, then (normal) click a link and go backward to the google result page, I am back at the top of the page instead of the "invisible" anchor from where I left this page.

This 3 bugs are related to webrender.

Sorry I got confused with my new driver I didn't realise I was getting WebRender automatically so it was back on after FF restart.

I have the 3 bugs with Fission ON. I have been using it since nearly two months without issue until a few weeks ago.

Thanks for investigating this further, moving it over to webrender. Can you please also provide us a copy of about:support?

Component: Untriaged → Graphics: WebRender
Flags: needinfo?(thanatos.sith)
Product: Firefox → Core

Hi Alexis - can you help see if you can reproduce this?

Blocks: wr-70
Flags: needinfo?(a.beingessner)
Priority: -- → P3

Wait hold on you've been running Fission for two months? And this issue goes away if you disable Fission?

Fission is still very unstable, and all of these bugs sound like things it could cause. We don't advise dogfooding it at the moment.

Flags: needinfo?(a.beingessner)

(In reply to Timea Babos from comment #5)

Thanks for investigating this further, moving it over to webrender. Can you please also provide us a copy of about:support?

Sorry it is a Fission bug, not WebRender.

If Fission is in a too early stage for now, I will stop using it and give it another go in a couple of months.

Flags: needinfo?(thanatos.sith)

Closing as invalid for now becauseo of Fission.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
See Also: → 1572887
You need to log in before you can comment on or make changes to this bug.