Open Bug 1813899 Opened 1 year ago Updated 5 months ago

Firefox Freezes on Pixel 6a plus subsequent reboot

Categories

(Fenix :: Browser Engine, defect, P5)

Product:
Fenix
Component:
Browser Engine
Platform:
All
Android
Type:
defect

Tracking

(Not tracked)

People

(Reporter: boek, Unassigned)

References

Details

Attachments

(1 file)

gzipped output from adb logcat, connected during my freeze
534.02 KB, application/gzip
Details

From github: https://github.com/mozilla-mobile/fenix/issues/28086.

Steps to reproduce

  1. The issue itself manifests entirely randomly. It can happen while scrolling any page. I have not found a reliable way to trigger the issue.

Expected behaviour

  1. The page should remain scrollable.

Actual behaviour

  1. The page completely freezes, including any part of Firefox's UI. This will remain in a frozen state for quite a while, until I get Android's "Firefox has stopped responding" message. Eventually, the phone would hard reboot.

Device name

Pixel 6a

Android version

Android 13

Firefox release type

Firefox

Firefox version

107.2.0

Device logs

I am unable to find the crash log within Firefox's settings. Furthermore, since I am unable to reliably reproduce the issue, I cannot create an ADB logcat. However, the issue seems to be affecting multiple people as can be seen in this Reddit topic with multiple recent posts as well: https://www.reddit.com/r/GooglePixel/comments/x56byt/any_pixel_6a_user_with_firefox/

Additional information

I was unable to copy/paste these logs, and before I could make more screenshots the phone would reboot. I am hoping these screenshots are helpful. If not, please let me know how I can obtain more relevant information taking into account that I cannot reliably reproduce the issue and that the phone will reboot quite soon after this bug, leaving me with little time to get anything worthwhile.



┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Capturing a performance profile might be useful here. Using the networking or graphics sections.

-- https://github.com/mozilla-mobile/fenix/issues/28086#issuecomment-1353689715

I've just had experienced a freeze (not a restart yet).

During the freeze, I was able to capture the following performance profile: https://share.firefox.dev/3ZbfEKT

I think it says the AndroidUI thread is busy-looping in org.mozilla.geckoview.GeckoSession$Compositor.syncPauseCompositor() ?

09:05 - captured 10-second firefox performance profile from a frozen firefox

09:10 - uploaded firefox performance profile
09:23 - closed firefox using an up-swipe (i.e. not a "force-stop"). I tried to capture a performance profile of this, but of course the capture aborted after firefox closed and did not capture anything.

  • re-opened firefox

Android did not restart this time, despite waiting an additional four minutes. It still has not restarted as of 0940.

adb logcat attached. Some extracts:

--------- beginning of crash
02-16 17:32:12.173 473 473 F libc : crash_dump helper failed to exec, or was killed
02-16 17:32:12.195 497 497 F libc : crash_dump helper failed to exec, or was killed
--------- beginning of kernel

[I did not notice a restart on 02-16, or have any other records. However Android uptime is about 137 hours, which appears consistent with the date of the "crash" log entry.]

02-22 09:02:24.866 1595 1786 W InputDispatcher: Not sending touch gesture to d76113e ActivityRecordInputSink org.mozilla.firefox/org.mozilla.fenix.HomeActivity because it is not responsive

02-22 09:05:34.012 17074 17105 I GeckoJavaSampler: Profiler starting. Calling thread: Gecko

02-22 09:05:45.038 16622 16673 I GeckoJavaSampler: Profiler stopping. Sample array position: 9681. Overflowed? false

02-22 09:23:06.753 17074 17105 I GeckoJavaSampler: Profiler starting. Calling thread: Gecko

02-22 09:23:13.403 1595 1672 I ActivityManager: Killing 19732:org.mozilla.firefox:utility/u0a238 (adj 905): remove task
02-22 09:23:13.404 1595 1672 I ActivityManager: Killing 17269:org.mozilla.firefox:gpu/u0a238 (adj 905): remove task
02-22 09:23:13.405 1595 1672 I ActivityManager: Killing 16622:org.mozilla.firefox:tab13/u0a238 (adj 905): remove task
02-22 09:23:13.405 1595 1672 I ActivityManager: Killing 17074:org.mozilla.firefox/u0a238 (adj 900): remove task
02-22 09:23:13.436 1595 1682 I libprocessgroup: Successfully killed process cgroup uid 10238 pid 19732 in 27ms

02-22 09:23:13.547 1595 10085 W ActivityManager: Scheduling restart of crashed service org.mozilla.firefox/org.mozilla.gecko.process.GeckoChildProcessServices$utility in 1000ms for connection
02-22 09:23:13.547 958 958 I Zygote : Process 19732 exited due to signal 9 (Killed)
02-22 09:23:13.549 1595 1682 I libprocessgroup: Successfully killed process cgroup uid 10238 pid 17269 in 0ms

02-22 09:23:13.639 1595 2106 W ActivityManager: Scheduling restart of crashed service org.mozilla.firefox/org.mozilla.gecko.process.GeckoChildProcessServices$tab13 in 10908ms for connection
02-22 09:23:13.639 958 958 I Zygote : Process 16622 exited due to signal 9 (Killed)

02-22 09:23:13.690 1595 2106 W WindowManager: Failed looking up window session=Session{54e674 1943:u0a10213} callers=com.android.server.wm.WindowManagerService.windowForClientLocked:5976 com.android.server.wm.WindowManagerService.removeWindow:2051 com.android.server.wm.Session.remove:230
02-22 09:23:13.736 1595 10025 W ActivityManager: Scheduling restart of crashed service org.mozilla.firefox/org.mozilla.gecko.process.GeckoChildProcessServices$gpu in 20811ms for connection
02-22 09:23:13.743 958 958 I Zygote : Process 17269 exited due to signal 9 (Killed)
02-22 09:23:13.745 1595 1682 I libprocessgroup: Successfully killed process cgroup uid 10238 pid 16622 in 0ms
02-22 09:23:13.745 1595 1682 I libprocessgroup: Successfully killed process cgroup uid 10238 pid 17074 in 0ms
02-22 09:23:13.788 1595 1672 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{4e474ec u0 org.mozilla.firefox/.App} t208 f}}
02-22 09:23:13.793 1595 10032 I WindowManager: WIN DEATH: Window{b01824c u0 org.mozilla.firefox/org.mozilla.firefox.App}

02-22 09:23:13.796 1595 2106 W ActivityManager: Scheduling restart of crashed service org.mozilla.firefox/org.mozilla.fenix.customtabs.CustomTabsService in 1000ms for connection
02-22 09:23:13.802 508 508 E BpTransactionCompletedListener: Failed to transact (-32)
02-22 09:23:13.802 508 508 E BpTransactionCompletedListener: Failed to transact (-32)
02-22 09:23:13.804 958 958 I Zygote : Process 17074 exited due to signal 9 (Killed)

02-22 09:23:36.108 15073 15073 D AndroidRuntime: Shutting down VM
02-22 09:23:36.110 15073 15073 E AndroidRuntime: FATAL EXCEPTION: main
02-22 09:23:36.110 15073 15073 E AndroidRuntime: Process: com.google.android.googlequicksearchbox:search, PID: 15073
02-22 09:23:36.110 15073 15073 E AndroidRuntime: com.facebook.litho.dr: Real Cause => java.lang.IllegalStateException: UrlHandler can only be used while the fragment is attached and state is not saved

02-22 09:23:36.270 1595 9052 I ActivityManager: Process com.google.android.googlequicksearchbox:search (pid 15073) has died: fg BTOP
02-22 09:23:36.270 1595 1682 I libprocessgroup: Successfully killed process cgroup uid 10144 pid 15073 in 0ms

02-22 09:23:36.272 1595 9052 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.nowoverlayservice.DrawerOverlayService in 1000ms for connection
02-22 09:23:36.272 1595 9052 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.search.googleapp.search.suggest.plugins.onesearch.server.OneSearchSuggestService in 11000ms for connection
02-22 09:23:36.273 1595 9052 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.frameworks.client.data.android.server.tiktok.SearchProcessEndpointService in 21000ms for connection
02-22 09:23:36.273 1595 9052 W ActivityManager: Scheduling restart of crashed service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.shared.util.keepalive.StandaloneKeepAlive$KeepAliveService in 31000ms for start-requested

02-22 09:23:41.274 1595 4178 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.mozilla.firefox/.App bnds=[813,1155][1023,1427]} from uid 10207

10:15 - Android restarted. I think very shortly after I suspended the computer, that the Android was plugged into. Either that, or I unplugged the Android first.

adb logcat no longer shows a "beginning of crash" entry at the start

--------- beginning of kernel
02-22 10:15:10.627 0 0 I trusty : boot args 0x*** 0x*** 0x1000 0x0
02-22 10:15:10.627 0 0 I trusty : gicc 0x***, gicd 0x***, gicr 0x***
02-22 10:15:10.627 0 0 I trusty : initializing trusty (Project: slider, Build: 9287263, Built: 21:49:12 Nov 13 2022)
--------- beginning of system
02-22 10:15:10.687 479 479 I vold : Vold 3.0 (the awakening) firing up

Severity: -- → S4
Priority: -- → P5

/me googles. I see Pixel's haven't sold very well :-).

P5 is your decision. Can S4 be explained? The entire browser freezes, and has to be restarted. It's surely at risk of losing state, e.g. form contents. Is it code for "I assume Google screwed up their phone (because the fault also triggers an OS restart), so I don't think it's really Firefox's fault"?

There's a bunch of reporters (using Pixel 6a). For me, the freeze happened between 1 or 2 times a week. I'm attempting to return the phone for a refund, much as I liked it otherwise.

If the user had just started trying Firefox on Android, I really think they'd give up.

Trying not to yell :-). Just want to make sure, that there's not something obvious we forgot to say.

  • My phone will be going back for a refund very soon (hurrah).

  • I have a new collection of Android "bug report" captures, and logs. I am happy to share. However, I am confused. They are from the same seemingly frozen process. But they are at different times, and they don't agree.

    The first "bug report" didn't blame syncPauseCompositor(), but instead android::NativeDisplayEventReceiver::dispatchVsync() -> art::JNI<false>::FindClass() -> art::ConditionVariable::WaitHoldingLocks().

    The second (an ANR file) blames syncPauseCompositor() -> pthread_cond_wait()

  • There were also hundreds of different threads called "EditToolbar-thread-1", "EditToolbar-thread-2", and "EditToolbar-thread-3" (but not -4 or -5 etc). At some very late point, Android wrote this ANR ("App Not Responding") file, but logged that it had timed out dumping stacks after a few seconds. My guess is it was struggling to dump all those hundreds of threads. In any case, they seem undesirable :-).

I'm experiencing the same issue Jeff is—regular crashing when scrolling. Pixel 6a with Android 13.

I'm not technically savvy, so I've no idea how to grab logs Apologies.

Hi Grái. FYI, "Priority: -- → P5" means "Will not fix, but will accept a patch".

AIUI, we are waiting for Google to fix their kernel (graphics drivers?) to stop the phone rebooting[*].
Or we need to recruit a skilled developer, to see if they can find a workaround in Firefox :-).
Or find a Firefox bug triage person who can explain this priority system.

I don't think we're waiting on more logs or comments from anyone.

[*] https://old.reddit.com/r/GooglePixel/comments/10jpcqs/pixel_6_reboots_short_time_after_firefox_freezes/ja7f0zz/?context=3

(But if anyone is interested in technical details, my link above has a bit more logs and analysis)

I think the problem is fairly distinctive. So you probably don't need to worry that you might have a different problem instead :-) -

Pixel 6a (and maybe Pixel 6?), Firefox randomly freezes while scrolling, e.g. once per week.

I personally didn't get any Android warning about Firefox not responding.

It is possible to close Firefox[*] and then resume using it. Sometime after the freeze, usually the whole phone reboots. (It was usually in a few minutes, when I closed Firefox and re-opened it? Maybe it takes longer if you don't do that?)

[*] https://support.google.com/android/answer/9079646?hl=en-GB

I might have found that repeated using the URL bar to navigate to new pages (and then scrolling) helps to trigger the bug a little faster. But it's hard be sure with these things :-).

(In reply to Alan Jenkins from comment #9)

I think the problem is fairly distinctive. So you probably don't need to worry that you might have a different problem instead :-) -

Pixel 6a (and maybe Pixel 6?), Firefox randomly freezes while scrolling, e.g. once per week.

I personally didn't get any Android warning about Firefox not responding.

It is possible to close Firefox[*] and then resume using it. Sometime after the freeze, usually the whole phone reboots. (It was usually in a few minutes, when I closed Firefox and re-opened it? Maybe it takes longer if you don't do that?)

[*] https://support.google.com/android/answer/9079646?hl=en-GB

I might have found that repeated using the URL bar to navigate to new pages (and then scrolling) helps to trigger the bug a little faster. But it's hard be sure with these things :-).

I am having exact same issue for months. This only happen to my pixel 6a. It does not happen on my old oneplus 6t.

If I switch to another browsers, they never hang, and no auto reboot. Once I switch back to firefox, firefox will hang randomly and auto reboot happens.

I have this issue too, and my own 6a always reboots 5 seconds after locking the screen; turning it on or staying on the phone prevents the reboot, and any audio playing though the 6a from any app prevents said reboot.
Not very consistently but prominently enough to recommend, I experience this issue mostly on AI generating websites, both text and image based ones.

I have this issue as well on my Pixel 6a. It's thankfully relatively rare, but it still happens from time to time.
It seems that the hard reboot happens as soon as the phone has gone to sleep (screen turns off). Whether I closed and restarted the frozen Firefox, or not, does not seem to matter.
For me, this often seems to happen on Reddit (I don't use the app, I go to their website). I'll just be scrolling and clicking around and suddenly the freeze happens. I haven't really found a pattern otherwise.

See Also: → 1853738

I can confirm this is also happening on my Pixel 6a for quite some time (months) now, same behavior as described in earlier comments.
A tab is freezing during scrolling. I cannot say it is happening on certain websites all the time. Sometimes it recovers, sometimes i need to force close and reopen Firefox. But in any case I know my 6a will reboot soon. As long as I keep the phone active, and keep using firefox it is fine. But as soon as I put it away, and it goes into sleep mode, phone will reboot.

I do have quite a number of open tabs (about 30 or so).
only addon I have active is ublock origin. I will try disabling it and try without it for couple of days.

Duplicate of this bug: 1853738

Wanted to add mine here as well. This has been happening to me for probably a year. Pixel 6a. Same as everyone else. Freeze during scrolling. Pixel reboots once it goes to sleep.

See Also: → 1825149

Ever since Android 14 released, I have not had any freezing or crashing since updating to it...though not sure if it was due to a new Firefox update or something else, but regardless, no issues so far.

I haven't yet upgraded to Android 14 on my 6a, but I haven't had any crashes for three weeks now. Maybe something related was addressed in Firefox 119?

Also on my end the issue has not resurfaced in past weeks. Probably since update firefox 119 was installed (mid-October).
And I am still holding off the Android 14 upgrade.

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

Attachment

General

Creator:
Created:
Updated:
Size: