Open Bug 1760572 Opened 2 years ago Updated 2 years ago

Tab load and reload fails after some hours

Categories

(Firefox :: Tabbed Browser, defect)

Product:
Firefox
Component:
Tabbed Browser
Version:
Firefox 98
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: hrdubwd, Unassigned, NeedInfo)

References

Details

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

Steps to reproduce:

Leave FF running with "Tab Reloader (page auto refresh)" extension working on several pinned tabs.

Actual results:

After some time, ranging from a couple of hours to a couple of days - no immediately obvious pattern - the tabs do not reload. F5, Ctrl-R, Shift-Ctrl-R all fail to have any effect. But then, no other tab will reload manually either, nor will new tabs.
On restarting FF all is good, for a while.
(The Tab reloader makes it obvious when the problem starts - hourglass ...)

Expected results:

Simply reload the tab.
This has started to occur, I think with 98.0.1, just possibly 98.0 (activity for a week or two has meant multiple restarts).
I have many tabs open at once, 54 GB RAM - never filled. The tabs are on many different sites so it is not the source problem. I cannot even reload my router's dashboard or any other device on my LAN.
Internet connection is good - email still runs (Thunderbird).

It has done it twice today - totally unresponsive to loading. This is going to be a pain.

I tried to run the profiler to capture the condition but of course when it occurs I cannot load the required page! (It has just happened again.) Any way out of that?

The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Tabbed Browser

I have now confirmed (numerous times) that the problem recurs even with extension 'Tab Reloader (page auto refresh)' disabled. It takes longer, and is first in evidence from tabs in which the content is refreshed by a push or a script (I assume). It has just occurred overnight when there was no user action whatsoever, not even entering the main password. I had to restart to do this now. Router, internet etc. have remained good in the meantime - no apparent fault.

The severity field 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)

Dr B W Darvell, do you see any errors in the browser console when this happens?

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

Sorry for the delay. I can see nothing specific. There are many errors with these titles:

  • TypeError: undefined has no properties
  • Exception { name: "NS_ERROR_NOT_AVAILABLE", message: "Component returned failure code: 0x80040111
  • Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist.
    but when the freeze occurs there seems to be nothing else happening anyway. There is no obvious critical point, but then I cannot predict when it happens (and the log keeps deleting itself - is that right?) and I do not know what I might be looking for anyway.
    Any guidance?
Flags: needinfo?(hrdubwd)

The severity field 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)

Hello! I have tried to reproduce the issue with firefox 107.0a1(2022-10-11) on Ubuntu 22.04, unfortunately I wasn't able to reproduce the issue on my end. Could you please answer the following questions in order to further investigate this issue?

  1. Does this issue happen with a new profile? Here is a link on how to create one: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
  2. Does this issue happen in the latest nightly? Here is a link from where you can download it: https://www.mozilla.org/en-US/firefox/channel/desktop/
  3. Do you have any addons installed if so can you list them?
Flags: needinfo?(hrdubwd)

Curiously, since last I reported the problem seems to have faded away slowly (without me changing anything except switching off Tab Reloader, which thereby delayed the problem but did not stop it, it just took longer to show because there were so much fewer reloads). Whether this is a Windows problem I could not say, but it did seem to start rather abruptly and I assume therefore it is to do with an FF update. What I will do now is reset the Tab Reloader, restart FF, and see whther it recurs. It would be very to hard to know whether either option you suggest could make a difference without that control check. I'll get back to you anyway to report the outcome.

Flags: needinfo?(hrdubwd)

I reactivated Tab Reloader. All seemed fine for a while, but it has just seized up again after less than a day.
I cannot work using a new profile I believe.
Updated Nightly now running: four tabs, each on 5 minute reload using Tab Reloader. We'll see what happens.

Current Nightly as described: after ~7 hours, two tabs jammed. One was reloaded after manual retry (twice), the other did not.
Reloaded: https://www.blitzortung.org/en/live_lightning_maps.php?map=12
Bad: https://www.snow-forecast.com/maps/dynamic/uk?over=none&symbols=snow&type=snow.next3days
OK so far: https://en.sat24.com/en/gb/rainTMC, https://en.sat24.com/en/gb/visual

So, nothing to do with profile or extensions. I'll leave it run.

Nightly crashed overnight - only Tab Reloader running.
Restarted, testing with 7 weather tabs.

The (then current at restart) Nightly instance was running with up to 40% of CPU being taken - slowing everything down. The tabs were still all active. I had to stop it. Will retry (now 108).

Hello Darvell! Thank you for the reply! Could you please attach the crash report from about:crashes?

Flags: needinfo?(hrdubwd)

There are two that appear to be relevant, submitted automatically, it seems:
Firefox 107.0a1 Crash Report [@ OOM | small ]
bp-e25620b0-b6fe-46ee-9ff4-74d170221020 2022-10-20, 10:28
bp-f7bc55d1-dcb4-43e3-9b5a-d44dd0221020 2022-10-20, 10:28
Please advise how I save these so that I can attach them here.

It appears that the reason for the crash was 'out of memory', which seems odd because I have 54 GB on board, the peak was 101.16%, and the current usage, with Nightly running with the same tabs, is 66.72% (says Process Explorer). Something very wrong there, I guess, for such a leak?

Thanks.

Flags: needinfo?(hrdubwd)

108.0a1 after a couple of days was taking 25% of CPU nearly continuously, a day or so later 2 of the 7 tabs had failed to load.
A crash occurred (dialog appeared), but the send from the dialog failed.
Howver, it then restarted automatically, about:crashes showed a new report which I then submitted successfully:
bp-b209f479-2d8f-431d-9e66-e0c5c0221025 2022-10-25, 12:37
I have now updated again (same version number, 2022-10-24), and will run for a while.

Looking at FF itself (106.0.1), the tab fails do not occur for those that have internal refresh or update. It is the reload either manually (inc loading of entirely new tabs) or using Tab Reloader (which I assume looks like manual in some key respect) that causes the lock. Sometimes this occurs on first starting FF! A restart then allows it to run normally (for a while, at least).

FYI: these 106.0.2 fixes "Fix page reloading not working with Firefox View and not refreshing synced data (bug 1792680 and bug 1794474)."
https://www.mozilla.org/en-US/firefox/106.0.2/releasenotes/
have not fixed this problem.

The Nightly ran for 6 days without a problem (supposed update still shows the same version number). FF had failed several times in that interval. I had to reboot, so starting Nightly again.

You need to log in before you can comment on or make changes to this bug.