Closed Bug 1854309 Opened 2 years ago Closed 2 years ago

GeckoView crashes on Xiaomi 12

Categories

(GeckoView :: General, defect, P2)

Product:
GeckoView
Component:
General
Version:
Firefox 116
Platform:
All
Android
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: fleig, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/117.0

Steps to reproduce:

We are running a business app that uses GeckoView as its display component. A customer reported that the app crashes on a Xiaomi 12 (5G Model 2201123G) after start (i.e. when GeckoView is launched).

Actual results:

The app crashes with a white screen when GeckoView is launched.

We've asked the customer to install Firefox from the Play Store. Firefox starts but crashes with a similar effect when navigating to a web site.

Expected results:

We'd expect to show GeckoView the start page of our app, Firefox is expected to show the web page. Both apps should not crash with white screen.

The severity field is not set for this bug.
:boek, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jboek)
Severity: -- → S2
Flags: needinfo?(jboek) → qe-verify+
Priority: -- → P2

Daniel

Is there a stack trace or other crash artifact that you can share?

QA: Do we have a Xiaomi 12 to test this one?

Hi!
I did try reproducing this issue on a Xiaomi Redmi Pad (Android 12) but without success.
The builds tested were RC 117.0 and latest Nightly 120.0a1 from 2023-10-06.
A few webpages were accessed, and navigated on, on both builds, without any crash.

Flags: qe-verify+

Dear all,

unfortunately currently we do not have access to that device. Our app does not send a crash log (what it does on application crashes), so we guess that it is not a "hard" crash, but more something like the screen just staying white.

Please note that according to our knowledge the Xiaomi "Redmi" series are different models than the "plain" Xiaomi 12.

Best regards,
Daniel

Sorry. I'm closing this bug as "incomplete" because it's not actionable without a crash report (from about:crashes) or steps to reproduce.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
Component: Core → General
You need to log in before you can comment on or make changes to this bug.