Closed Bug 1599246 Opened 5 years ago Closed 5 years ago

New tabs are unresponsive after unlocking session

Categories

(Core :: Performance: Responsiveness, defect, P2)

Product:
Core
Component:
Performance: Responsiveness
Version:
70 Branch
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Project Flags:
Performance Impact medium

People

(Reporter: roger, Unassigned)

Details

(Keywords: perf:responsiveness)

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

Steps to reproduce:

Unlock PC, open a new tab, enter address.
OR: Unlock PC, click on a link in (e.g.) Slack that wants to open a new tab.

OS details: Linux Mint 18.3, Cinnamon. Firefox 70.0.1. This problem started happening in Firefox 70; haven't seen it before.

Actual results:

Firefox hangs. Tab displays progress back-and-forth thing, nothing happens. UI becomes unresponsive. Have to "killall firefox-bin" to recover.

Expected results:

Tab should correctly display webpage.

Note that this happens several times a day.

More symptoms:

After unlock:

  • I can open developer tools.
  • YouTube videos that were already open don't resume.
  • If I have a tab that was unloaded -- i.e. from the previous time this happened, and I've not yet clicked on it to rehydrate it, it gets stuck in the progress-back-and-forth mode.

I cannot reproduce this issue on an Ubuntu16 and we do not have Linux Mint so I can't confirm it, however, this sounds like a very general issue. I will set it component to (Core) Performance. I fairly sure this isn't a correct component; please change it to a more appropriate one if incorrect.

@reporter: Will you please respond to some questions?

  1. What do you mean by "hang"? Do you mean to say it froze and could not be used even if you waited for a minute or 2? Did you need to kill firefox and reopen it to be able to use it again?
  2. Did it start happening in Firefox Release v70.0?

Hopefully, some developers will know how to address this better?

Thank you for your contribution!

Component: Untriaged → Performance
Flags: needinfo?(roger)
Product: Firefox → Core

What do you mean by "hang"? Do you mean to say it froze and could not be used even if you waited for a minute or 2?

Yes. Firefox freezes.

Did you need to kill firefox and reopen it to be able to use it again?

Yes. killall firefox-bin and then restart the session.

Did it start happening in Firefox Release v70.0?

Yes. Didn't see it in Firefox 69. Since upgrading to 70.0, I'm seeing it multiple times a day.

Flags: needinfo?(roger)

Hi roger,
thanks for the bug report, do you mind provide a profile to us so we can investigate more? It's basically about using the Gecko Profiler https://profiler.firefox.com/ to take a profile and share with us.

And also do you mind using moz-regression (https://mozilla.github.io/mozregression/) to see which changeset caused it?

Flags: needinfo?(roger)
Priority: -- → P2
Whiteboard: [qf:p2:responsiveness]

Will do. I'm on 71.0 (since yesterday) and the problem hasn't happened yet. It used to happen a couple of times a day, so I'll keep an eye out for it.

Flags: needinfo?(roger)

Still haven't seen this happen in 71.0. Call it cantreproduce?

That is great! I will set the bug as WORKSFORME, but if you see it again please reopen this bug adding the appropriate information.

Thank you for your contribution!

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Performance Impact: --- → P2
Keywords: perf:responsiveness
Whiteboard: [qf:p2:responsiveness]
Component: Performance: General → Performance: Responsiveness
You need to log in before you can comment on or make changes to this bug.