Firefox on android fails to start (force closed immediately)
Categories
(Fenix :: General, defect, P2)
Tracking
(Not tracked)
People
(Reporter: dirfter2005, Unassigned)
References
Details
Attachments
(1 file)
1.88 MB,
application/x-zip-compressed
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 Edg/120.0.0.0
Steps to reproduce:
Launch the firefox app after installing it from Google Play
Actual results:
Firefox app is about to start (homepage appears) but then closes immediately and returns to the home screen.
phone details:
POCO X5 5G, with MIUI 14 EU ROM (android13), rooted
Expected results:
should be launched normally into homepage
(update)
I found I can launch firefox app normally if clearing all its data and reboot my device, unless I reboot my device again.
Once I do so and then launch firefox, it will start to be force closed again.
Therefore, I cleared firefox's data (app kept) and launched it so as to tap "Crashes" in firefox's settings to send you a crash report. However, no report found in it.
(Due to removal of app data...?)
But without clearing it, I can't launch firefox (force closed) to tap "Crashes" to get the crash report.
Now caught in a dilemma...
Comment 2•1 year ago
|
||
Could you help getting adb log of the forced close and attaching here?
You could see this comment to find how to get adb log: https://bugzilla.mozilla.org/show_bug.cgi?id=1816330#c9
(In reply to jackyzy823 from comment #2)
Could you help getting adb log of the forced close and attaching here?
You could see this comment to find how to get adb log: https://bugzilla.mozilla.org/show_bug.cgi?id=1816330#c9
Hello,
My log file is too large to be attached here, so I uploaded it to my GDrive instead:
https://drive.google.com/file/d/1lkbbjn5iKk3OlH8MEPdtrai8jVWKBhqV/view?usp=drive_link
Thanks for your help.
Comment 4•1 year ago
|
||
https://drive.google.com/file/d/1lkbbjn5iKk3OlH8MEPdtrai8jVWKBhqV/view?usp=drive_link
It asks for requesting permission.
I'd recommend you to compress the log (zip or other format) and then upload here / or make the google drive link public visible.
Sorry for forgetting that it can be compressed.
Thanks for your help.
Comment 6•1 year ago
•
|
||
Thanks for the log.
I'm not sure but it looks like the bug 1864557
Comment 7•1 year ago
|
||
Sorry for the wrong hint.
The possible error is here
01-02 19:29:50.983 8650 10262 I AbstractFirebasePushService: Got new Firebase token: d29iMHtGSbqNvrXPj6CbZy:APA91bGbQGeZCh5utXuBJL1KT0YpnmdEmmO8mqGvUVkPIB_bVqNNVXU8gcBWSTkRnVW4MGCfj5fg1fL_Tvx5MwEI1Au36ZmanA8zShIzG6qZ446F8avf3XM7JPcCjiP5ZNpwVU2ZED5z
01-02 19:29:50.984 8650 10112 I AutoPushFeature: Received a new registration token from push service.
01-02 19:29:50.989 8650 10112 I push::internal::push_manager: saved the registration ID but not telling the server as we have no subs yet
01-02 19:29:50.990 8650 10112 I push::internal::communications::rate_limiter: Resetting. now(1704194990) - 0 < 86400 for verify_connection.
01-02 19:29:50.994 8650 10112 I push::internal::communications::rate_limiter: Allowed to pass through for verify_connection!
01-02 19:29:50.995 8650 10112 W AutoPushFeature: Internal error occurred in AutoPushFeature.
01-02 19:29:50.995 8650 10112 W AutoPushFeature: mozilla.appservices.push.PushApiException$InternalException: Internal Error: General Error: "No subscriptions created yet."
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.FfiConverterTypePushApiError.read(push.kt:3)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.FfiConverterTypePushApiError.read(push.kt:1)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.FfiConverter$DefaultImpls.liftFromRustBuffer(push.kt:13)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.FfiConverterRustBuffer$DefaultImpls.liftFromRustBuffer(push.kt:6)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.FfiConverterTypePushApiError.liftFromRustBuffer(push.kt:2)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.FfiConverterTypePushApiError.liftFromRustBuffer(push.kt:1)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.FfiConverterRustBuffer$DefaultImpls.lift(push.kt:7)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.FfiConverterTypePushApiError.lift(push.kt:3)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.FfiConverterTypePushApiError.lift(push.kt:2)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.PushApiException$ErrorHandler.lift(push.kt:2)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.PushApiException$ErrorHandler.lift(push.kt:1)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.PushKt.checkCallStatus(push.kt:75)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.PushKt.access$checkCallStatus(push.kt:1)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.appservices.push.PushManager.verifyConnection(push.kt:68)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.components.feature.push.AutoPushFeature$verifyActiveSubscriptions$1.invoke(AutoPushFeature.kt:10)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at mozilla.components.feature.push.AutoPushFeature$withConnection$2$1.invokeSuspend(AutoPushFeature.kt:8)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:112)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
01-02 19:29:50.995 8650 10112 W AutoPushFeature: at java.lang.Thread.run(Thread.java:1012)
01-02 19:29:51.041 2053 5902 I SmartPower.org.mozilla.firefox/10255(8650): visible->died(2403ms) R(process died ) adj=0.
01-02 19:29:51.041 826 826 I Zygote : Process 8650 exited cleanly (11)
01-02 19:29:51.042 2053 5902 I ActivityManager: Process org.mozilla.firefox (pid 8650) has died: fg TOP
Comment 9•1 year ago
|
||
I think that exception is unrelated - it really shouldn't be reported, but it's harmless. The logcat appears to show the app dieing twice:
01-02 19:29:51.040 2053 3186 I WindowManager: WIN DEATH: Window{a580443 u0 org.mozilla.firefox/org.mozilla.firefox.App}
01-02 19:29:51.041 2053 5902 I SmartPower.org.mozilla.firefox/10255(8650): visible->died(2403ms) R(process died ) adj=0.
01-02 19:29:51.041 2053 3186 W InputManager-JNI: Input channel object 'a580443 org.mozilla.firefox/org.mozilla.firefox.App (client)' was disposed without first being removed with the input manager!
01-02 19:29:51.041 826 826 I Zygote : Process 8650 exited cleanly (11)
01-02 19:29:51.042 2053 2685 I SmartPower: org.mozilla.firefox/10255 state=foreground adj=0 proc size=3 move to background process died
01-02 19:29:51.042 2053 5902 I ActivityManager: Process org.mozilla.firefox (pid 8650) has died: fg TOP
01-02 19:29:51.042 2053 2383 I libprocessgroup: Successfully killed process cgroup uid 10255 pid 8650 in 0ms
and
01-02 19:29:56.222 10459 10492 W GeckoThread: zerdatime 612427 - runGecko
01-02 19:29:56.315 2053 3616 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(uid/pid:10255/8652, [NetworkRequest [ REQUEST id=143, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VCN_MANAGED Uid: 10255 RequestorUid: 10255 RequestorPkg: org.mozilla.firefox UnderlyingNetworks: Null] ]], android.os.BinderProxy@9267ae6)
01-02 19:29:56.315 2053 2473 I WindowManager: WIN DEATH: Window{564705a u0 org.mozilla.firefox/org.mozilla.firefox.App}
01-02 19:29:56.315 2053 2473 W InputManager-JNI: Input channel object '564705a org.mozilla.firefox/org.mozilla.firefox.App (client)' was disposed without first being removed with the input manager!
01-02 19:29:56.316 2053 2581 D ConnectivityService: releasing NetworkRequest [ REQUEST id=143, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VCN_MANAGED Uid: 10255 RequestorUid: 10255 RequestorPkg: org.mozilla.firefox UnderlyingNetworks: Null] ] (release request)
01-02 19:29:56.316 2053 2581 D ConnectivityService: teardown wifi type 1 state: CONNECTED primary: true
01-02 19:29:56.316 2053 2581 D ConnectivityService: nai type 1 state: CONNECTED primary: true
01-02 19:29:56.316 826 826 I Zygote : Process 8652 exited cleanly (11)
01-02 19:29:56.316 2053 5885 I SmartPower.org.mozilla.firefox/10255(8652): visible->died(1577ms) R(process died ) adj=0.
01-02 19:29:56.317 2053 5885 I ActivityManager: Process org.mozilla.firefox (pid 8652) has died: fg TOP
01-02 19:29:56.317 2053 2383 I libprocessgroup: Successfully killed process cgroup uid 10255 pid 8652 in 0ms
01-02 19:29:56.317 2053 2685 I SmartPower: org.mozilla.firefox/10255 state=foreground adj=0 proc size=4 move to background process died
01-02 19:29:56.319 2053 2671 E ProcessManager: error write exception log
Hopefully someone from the Fenix team can offer more insights.
Comment 10•1 year ago
|
||
ActivityManager: Process org.mozilla.firefox (pid 8652) has died: fg TOP
According to https://android.stackexchange.com/questions/249592/process-has-died-cch-cacc, this implies an out-of-memory situation, and the log is reflecting that it did indeed kill a foreground app (which it tries not to do). I'll ask the Android team and point them at this bug.
Comment 11•1 year ago
|
||
If it is OOM ,then it really looks like bug 1864557.
However STR is a bit different?
Comment 12•1 year ago
|
||
I'd say it may be related to the same root cause of the OOM that causes bug 1864557, but while it is not identified it seems hard to make sure both bugs are strictly related.
Comment 13•1 year ago
|
||
The severity field is not set for this bug.
:matt-tighe, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Updated•9 months ago
|
Comment 14•7 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Fenix::Push' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 15•7 months ago
|
||
Back to General as the core issue is still unclear.
Description
•