1786388 - Hanging when navigating to URLs, using devtools, or downloading update.

Status: RESOLVED DUPLICATE of bug 1786242

(Firefox :: General, defect)

Description

[AMWiederin]

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

Steps to reproduce:

Typing google.com in the address bar and hitting enter has no result.
Using the arrow button in the bar instead of Enter starts loading, but eventually ends in a "The connection has timed out" error.
Refreshing an already-open page does work, but sometimes shift-refresh is needed.

Sometimes video buffering hangs indefinitely and requires a page refresh.

After opening devtools with F12, the Network and Console panes remain empty for a long time, and console commands have no output.

When an update is available, after going to the "Help → About Nightly" window, the download stays at 0% for a long time. Restarting Firefox allows the download to finish, and then restarting again completes the update.

I ran mozregression; this was the last regression window output:
2022-08-22T15:36:16.293000: INFO : Narrowed integration regression window from [a3cd22f7, aa9a4f02] (4 builds) to [7696ca8c, aa9a4f02] (2 builds) (~1 steps left)

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 2

[Julian Descottes [:jdescottes]]

Thanks for filing, moving to Firefox General.

Some additional questions first.

Can you confirm if you still have the issue?

Adding the link to the regression window mentioned in the summary https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=7696ca8c&tochange=aa9a4f02

After opening devtools with F12, the Network and Console panes remain empty for a long time, and console commands have no output.

Can you attach a screenshot of the Network and Console panel?

Comment 3

[AMWiederin]

Attachment: devtools screenshot

(In reply to Julian Descottes [:jdescottes] from comment #2)

Can you confirm if you still have the issue?

Yes, I it is still happening as of 106.0a1 (2022-08-25) (64-bit), though it's somewhat inconsistent.

Can you attach a screenshot of the Network and Console panel?

Attached. Though the screenshot is for about:blank, the console behavior still happens as shown, and the Network pane is exactly the same when it happens for other pages.

Comment 4

[Julian Descottes [:jdescottes]]

I wonder if this is the same issue as Bug 1786242?

Could you try with a clean profile to see if this is profile-related?

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Yes, it sounds similar but the regression range doesn't really fit. For the other bug we see inconsistent behaviors since the merge from autoland to mozilla-central on August 12th. Maybe you can check for the regression range again? Thanks!

Comment 6

[Arthur K. (he/him)]

Hi,

Chiming in here because I noticed some major hanging and large mem use recently with 105.0b1. Can you guys take a peek at https://bugzilla.mozilla.org/show_bug.cgi?id=1778214#c17 and tell me if it seems in the same wheelhouse as this memory leak / dev tools hanging?

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Not sure how often this hanging happens but I think that it is the same as the bug Julian mentioned.

AMWiederin, would you mind to test the next scheduled nightlies that will be shipped in 4-5hr? If you want to do it earlier you could also use the below build which should have a fix:

https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/XdZ1AQN6Spe3g-lFRUbf-w/runs/0/artifacts/public/build/target.zip

Thanks.

Comment 8

[AMWiederin]

(In reply to Henrik Skupin (:whimboo) [⌚️UTC+2] from comment #7)

Not sure how often this hanging happens but I think that it is the same as the bug Julian mentioned.

AMWiederin, would you mind to test the next scheduled nightlies that will be shipped in 4-5hr? If you want to do it earlier you could also use the below build which should have a fix:

https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/XdZ1AQN6Spe3g-lFRUbf-w/runs/0/artifacts/public/build/target.zip

Thanks.

Hi, sorry for the late response. Yes the bug seems fixed for me now, at least with version 106.0a1 (2022-09-01) (64-bit).
Thank you so much for the help!

Comment 9

[Julian Descottes [:jdescottes]]

Thanks for checking! I would mark this as duplicate then, since the other bug contains all the relevant regression information.