Crash in [@ mozilla.appservices.relay.InternalException: at mozilla.appservices.relay.RelayKt.uniffiCheckCallStatus(relay.kt:40)]
Categories
(Firefox for Android :: Privacy, defect)
Tracking
()
People
(Reporter: clouseau-bot, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash, topcrash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/a3ebb3b3-0e34-4071-b8f0-42d410261015
Top 10 frames:
0 mozilla.appservices.relay.RelayKt uniffiCheckCallStatus toolkit/components/uniffi-bindgen-gecko-js/android/components/relay/android/src/main/java/mozilla/appservices/relay/relay.kt
1 mozilla.appservices.relay.RelayKt access$uniffiCheckCallStatus toolkit/components/uniffi-bindgen-gecko-js/android/components/relay/android/src/main/java/mozilla/appservices/relay/relay.kt
2 mozilla.appservices.relay.RelayClient fetchProfile toolkit/components/uniffi-bindgen-gecko-js/android/components/relay/android/src/main/java/mozilla/appservices/relay/relay.kt
3 mozilla.components.service.fxrelay.FxRelayImpl$fetchProfile$2$2 invokeSuspend mobile/android/android-components/components/service/firefox-relay/src/main/java/mozilla/components/service/fxrelay/FxRelay.kt
4 mozilla.components.service.fxrelay.FxRelayImpl$fetchProfile$2$2 invoke mobile/android/android-components/components/service/firefox-relay/src/main/java/mozilla/components/service/fxrelay/FxRelay.kt
5 mozilla.components.service.fxrelay.FxRelayImpl handleRelayExceptions mobile/android/android-components/components/service/firefox-relay/src/main/java/mozilla/components/service/fxrelay/FxRelay.kt
6 mozilla.components.service.fxrelay.FxRelayImpl$fetchProfile$2 invokeSuspend mobile/android/android-components/components/service/firefox-relay/src/main/java/mozilla/components/service/fxrelay/FxRelay.kt
7 mozilla.components.service.fxrelay.FxRelayImpl$fetchProfile$2 invoke mobile/android/android-components/components/service/firefox-relay/src/main/java/mozilla/components/service/fxrelay/FxRelay.kt
8 kotlinx.coroutines.intrinsics.UndispatchedKt startUndispatched
9 kotlinx.coroutines.BuildersKt__Builders_commonKt withContext
There is 1 crash in nightly 160 with buildid 20261014215550.
This bug looks actionable because:
-
A Rust panic inside
RelayClient::fetch_profilereaches Kotlin asmozilla.appservices.relay.InternalException, whichFxRelayImpl.handleRelayExceptionsdoes not catch, so the profile fetch crashes Fenix.FxRelayImpl.fetchProfilerunsclient.fetchProfile()insidehandleRelayExceptions, whose only catch clause iscatch (e: RelayApiException).- The generated binding
RelayClient.fetchProfilecallsuniffi_relay_fn_method_relayclient_fetch_profilethroughuniffiRustCallWithError(RelayApiException), so ordinary Rust errors come back as a caughtRelayApiException. - When the Rust call returns a panic status,
uniffiCheckCallStatusthrowsInternalException(a plainkotlin.Exception) instead of lifting aRelayApiException. - That exception is not caught by
handleRelayExceptions,fetchProfileorfetchAccountDetails, and it terminates the parent process from theDispatchers.IOcoroutine.
The exception class and frame 0 (
uniffiCheckCallStatus), withfetchProfileandhandleRelayExceptionsabove it, match this chain. The panic message is not in the report. The Rustfetch_profilebody has no explicit panic and sends through viaductClient::send_sync(pollster::block_on) to the registered backend, which is the likely source but is not shown here. First, look at whetherhandleRelayExceptionsshould also handleInternalException, so a Relay background fetch cannot crash the browser. Then look at what panics in the Rust relay/viaduct path on Android. -
The failing code comes from c0ac317234cf (gh) (bug 1977879) by gela.
Code references:
- mozilla::components::service::fxrelay::FxRelayImpl::handleRelayExceptions
- mozilla::components::service::fxrelay::FxRelayImpl::handleRelayExceptions
- mozilla::appservices::relay::RelayClient::fetchProfile
- mozilla::appservices::relay::InternalException
- relay::RelayClient::fetch_profile
- viaduct::client::Client::send_sync
gela, can you have a look please?
Filed automatically by Clouseau, which analyses nightly crashes with an LLM. Nothing above was written or checked by a human. Please close it as INVALID if it is wrong — that is useful feedback, not a nuisance.
This is not an independent Mozilla discovery: the crash is known here only because somebody submitted the crash report linked at the top. If this duplicates an existing report, please resolve THIS bug as the duplicate and leave the credit with the earlier reporter.
Comment 1•1 month ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 AArch64 and ARM crashes on nightly
For more information, please visit BugBot documentation.
Updated•1 month ago
|
Updated•22 days ago
|
Description
•