Open Bug 1606640 Opened 4 years ago Updated 2 years ago

opening a link in a new tab results in a blank page / inactive tab

Categories

(Core :: DOM: Content Processes, defect, P3)

Product:
Core
Component:
DOM: Content Processes
Version:
71 Branch
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: jarnix, Unassigned)

References

Details

(Keywords: regression)

Attachments

(2 files)

Screenshot from 2020-01-27 14-03-25.jpg
413.39 KB, image/jpeg
Details
Screenshot from 2020-01-27 13-50-27_01.jpg
71.94 KB, image/jpeg
Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

one of these 3 actions, randomly (not all the time):

  • click a link in a new tab
  • open a new tab and enter the url and press enter
  • click search on google

Actual results:

=> the new tab does not load, is frozen, I cannot open the dev console (F12 does nothing).

Expected results:

the new tab should have displayed the requested url

Hi Julien, thank you for reporting this. Unfortunately I wasn't able to reproduce the issue using Ubuntu 18.04 LTS with Firefox versions 71, 72 and 73. Can you try to see if you have the same problems with a clean profile and the latest Firefox Nightly?

Flags: needinfo?(jarnix)

Hello :)

I tried the nightly after your reply, for 2 days and I got the issue again two or three times. The tab is empty, it looks like it's waiting for something (I remember a spinner in the address bar or the load icon), but the status bar is empty, I cannot open the console (by pressing F12), I just have to close the tab and try again.

I started with a new profile. I already did it with the 71 version that I was using, same result. I have also sync enabled, I did not change anything else or do not remember.

I have only two extensions enabled : ublock and lastpass, which are really common extensions so I don't think it's coming for one of them.

I read on a reddit post that someone else had this issue, it was an old post though, but it said that the issue did not appear when hardware acceleration was disabled. I disabled it just now and will update the comment here.

Is there anything that I can look (like logs or something) to diagnose it further?

Flags: needinfo?(jarnix)

Hi Julien,

Thank you for your response. You could try to capture a performance profile by using the Cleopatra add-on. You can find more information on the add-on (how to install and use) by going here: https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler
https://perf-html.io/.
Also, please note that this add-on only works on Firefox Nightly, thus you need to be able to reproduce the issue on Nightly first. Here you can find the link to the latest Firefox Nightly: https://nightly.mozilla.org/.

Flags: needinfo?(jarnix)

Hi Alexandra,

I have the issue again. I can start the Gecko profiler, but I have to close the tab for the profiler to get the profile or it says that it could not contact the profiler within 30 seconds, so I don't know if the profile is interesting. I could reproduce the issue twice so I got 2 traces :

https://perfht.ml/2th61kD

https://perfht.ml/2TqpidQ

I hope it's useful.

Flags: needinfo?(jarnix)

Hi,

Thank you for the performance profiles, maybe it could help our developers in figuring out the cause of the problem.

I am not sure about the component, but I am assigning it to Firefox: Tabbed Browser, seems to be a good place to start. Please change it, if it's not suitable, maybe Memory Allocator could be better?

Component: Untriaged → Tabbed Browser

Any errors in the browser console when this happens? Make sure to set devtools.chrome.enabled = true before. https://developer.mozilla.org/en-US/docs/Tools/Browser_Console

Flags: needinfo?(jarnix)

Hello,
I cannot open the console (in the new tab) when the problem happens. I cannot refresh the tab, I just have to close it and open it again (sometimes the issue happens a few times in a row).
If you mean the opener's console, I can check the next time I see the problem and will update here.
Thanks

Flags: needinfo?(jarnix)

I set the devtools.chrome.enabled to true. I will try to see what it says. I have the issue almost all day long...

(In reply to Julien Ricard from comment #7)

I cannot open the console (in the new tab) when the problem happens. I cannot refresh the tab, I just have to close it and open it again (sometimes the issue happens a few times in a row).
If you mean the opener's console, I can check the next time I see the problem and will update here.

I mean the browser console, not the web console. See https://developer.mozilla.org/en-US/docs/Tools/Browser_Console

I got it, the browser console is open but I cannot see anything happening. All log levels are displayed.
I tried to strace the pid of the tab, it's stuck:

strace: Process 28815 attached
read(6,

(that's all). I can help you more, I can find some time for this since it's happening like 200 times per day. I can type command in the browser console or get logs, anything you might need.

The loading icon is animating in the tab but it's stuck. I can change the url in the address bar but nothing happens.

(In reply to Julien Ricard from comment #10)

I can help you more, I can find some time for this since it's happening like 200 times per day. I can type command in the browser console or get logs, anything you might need.

Finding a regression range might help: https://mozilla.github.io/mozregression/

Keywords: regressionwindow-wanted

The priority flag is not set for this bug.
:dao, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dao+bmo)
Flags: needinfo?(dao+bmo)

The priority flag is not set for this bug.
:dao, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dao+bmo)

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Keywords: regression

I'm currently trying to see what mozregression might tell me.

Hi, I think I found when the bug happened for the first time, it was on the 2018-10-11. I attached the screenshot of Mozregression.

I think it's not coming from the tab module, the status bar shows a status like "Transferring data" or "Waiting for (a domain)", which makes me think that the browser started to get the elements but does not render anything.

Julien, thanks for narrowing down the regression range. Could you please paste here the pushlog_url link seen in the Mozregression-gui window?

Flags: needinfo?(dao+bmo) → needinfo?(jarnix)
Priority: -- → P3

Hi, I had to run it again, so here are the results of the bisection:

app_name: firefox
build_date: 2018-10-11
build_file: /home/julien/.mozilla/mozregression/persist/2018-10-11--mozilla-central--firefox-64.0a1.en-US.linux-x86_64.tar.bz2
build_type: nightly
build_url: https://archive.mozilla.org/pub/firefox/nightly/2018/10/2018-10-11-22-01-18-mozilla-central/firefox-64.0a1.en-US.linux-x86_64.tar.bz2
changeset: 0de23e038872cb0986d7259e16ff966fcc050ae0
pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6f8701d1be0ccf42a8e22bfce6f40056a4f58a1b&tochange=0de23e038872cb0986d7259e16ff966fcc050ae0
repo_name: mozilla-central
repo_url: https://hg.mozilla.org/mozilla-central

Removing the regression window wanted flag, as the regression window was provided. Thanks @Julien.
If another regression range is required, please feel free to drop a comment and add the flag back.

Keywords: regressionwindow-wanted

(In reply to Julien Ricard from comment #22)

pushlog_url: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6f8701d1be0ccf42a8e22bfce6f40056a4f58a1b&tochange=0de23e038872cb0986d7259e16ff966fcc050ae0

I'm merely guessing here but bug 1470280 is in that range. Julien, can you still reproduce the bug if you set dom.ipc.processCount to 4 or lower in about:config?

Flags: needinfo?(jarnix)

Hi Dão, I just set this value. I will report here if it fixed the issue.

Flags: needinfo?(jarnix)
Severity: normal → --
Component: Tabbed Browser → DOM: Content Processes
Priority: P3 → --
Product: Firefox → Core
See Also: → 1654130
Severity: -- → S3
Priority: -- → P3

(In reply to Dão Gottwald [::dao] from comment #24)

I'm merely guessing here but bug 1470280 is in that range. Julien, can you still reproduce the bug if you set dom.ipc.processCount to 4 or lower in about:config?

(In reply to Julien Ricard from comment #25)

Hi Dão, I just set this value. I will report here if it fixed the issue.

Hi Julien, have you still seen this problem after setting your dom.ipc.processCount value to 4 or lower in about:config?

Flags: needinfo?(jarnix)

Not seen recently here (80.0.b3/4). Will report back if it recurs.

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.

Flags: needinfo?(jarnix)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: