Regular UI unresponsiveness on mac

RESOLVED WORKSFORME

Status

()

Firefox
General
RESOLVED WORKSFORME
2 years ago
2 years ago

People

(Reporter: glandium, Unassigned)

Tracking

40 Branch
x86_64
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
My wife has seen this regularly, apparently since upgrading to 40. The UI would become unresponsive to clicks, except the menu bar.

What kind of extra information would help debug this?
(Reporter)

Updated

2 years ago
Version: 38 Branch → 40 Branch
(Reporter)

Comment 1

2 years ago
Some more observation (happened twice today): the UI is not completely frozen. It is still possible to e.g. switch tabs and use the url bar, open web sites, etc. except any interaction takes > 30s or minutes. Interestingly, once in the url bar, typing doesn't show anything in the url bar itself, but the dropdown with suggestions shows up and is updated smoothly.

I tried to kill -11 the firefox process to trigger a crash report to have some idea of what's going on, unfortunately, it leads to OSX's crash reporter, not ours.
(Reporter)

Comment 2

2 years ago
New observation, after a while leaving it alone, it unsticks itself. Unfortunately, despite all telemetry being enabled, about:telemetry doesn't show any collected data for browser/thread hangs :(
Does this mean those hangs are completely missed in the data we (Mozilla) have, or do we have some other way they are collected, but doesn't appear in about:telemetry?
Flags: needinfo?(vladan.bugzilla)
(Reporter)

Comment 3

2 years ago
Yet another observation: this /may/ be correlated with the mac waking up from sleep.
> Unfortunately, despite all telemetry being enabled, about:telemetry doesn't
> show any collected data for browser/thread hangs :(

Because this is Release channel, Telemetry's chromehang and background-hang-reporter instrumentation is disabled.

> Does this mean those hangs are completely missed in the data we (Mozilla)
> have, or do we have some other way they are collected, but doesn't appear in
> about:telemetry?

The unresponsiveness is reported via Telemetry but not the information necessary to figure out where it's coming from.

Have you tried profiling the hang with the Gecko Profiler?
Flags: needinfo?(vladan.bugzilla)
(Reporter)

Comment 5

2 years ago
This hasn't happened once since upgrading to 41.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.