1607799 - rpubs.com crashes Firefox for Android (possibly OOM?)

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect, P1)

Description

[Sky Schubert [:skyschub]]

Attachment: logcat output. Crash happens at around 16:42:44

We have received a report that loading https://rpubs.com/acolumbus/how-to-use-r-with-excel on Firefox for Android crashes the browser. I can reliably reproduce the crash, and attached the logcat output to this bug. To me, this looks like we're running out of memory, but I'd appreciate if someone with more experience could confirm.

Fenix is handling the site just fine, so I'm wondering if there is even anything we can do about that, but I figured filing the issue is a good idea either way. :)

Comment 1

[Marcia Knous [:marcia]]

Do you get a crash report from Fennec? If so please paste the ID here. Thanks!

Comment 2

[Sky Schubert [:skyschub]]

I did not.

Comment 3

[Marcia Knous [:marcia]]

I tried using my Pixel 3 on Fennec release and the crash reporter didn't come up.

Comment 4

[Stefan Arentz | :st3fan | ⏰ EST | he/him]

Crashes on my Pixel 2 XL. No crash report is submitted unfortunately. Asking QA to take a look.

Comment 5

[Laurentiu Apahidean]

I have tested the issue on Release 68.4.1 and Beta 68.5b2 using a Samsung Galaxy S8+ (Android 8.0.0) and Google Pixel 3a XL (Android 10) and can confirm that Firefox crashes when accessing the page in question without generating a crash report. The issue does not occur on any Firefox Preview builds. Please let me know if there is further information I could help you with.

Comment 6

[Diana Rus]

This may be related to bug1574804.

Comment 7

[Petru-Mugurel Lingurar [:petru]]

When trying to load https://rpubs.com/acolumbus/how-to-use-r-with-excel on a Samsung S7 with 2 GB RAM I got the same as in the logcat posted in comment 0:

• (probably all) background running user applications are killed by the system with SIGKILL
• ultimately our foreground app is also killed with SIGKILL
  On my device the application does not exceed 200 MB in memory but indeed I saw the available system memory going down to just ~200 MB.
  The crash reporter would not show up because the app was killed by the system because of low memory, it did not crash.

The website did load in Fennec running on a Note 10 after it got to consume 2.5 GB RAM.

As to why this does not happen in Fenix, I suspect the underlying issue has been resolved in the meantime. Fenix uses a newer version of Gecko.

Asking Stefan on how to proceed with this.

Comment 8

[Laurentiu Apahidean]

I have retested the issue on Release 68.5.0 and Beta 68.6b1. The website loads without problems on a Samsung Galaxy Note9 (Android 9), but I am still able to reproduce the issue on a Google Pixel 3 (Android 9) and Samsung Galaxy S9 (Android 8.0.0).

Comment 9

[Stefan Arentz | :st3fan | ⏰ EST | he/him]

Since this is works well on Fenix (Firefox Preview), which as a much more recent Gecko, I am going to close this as WONTFIX for Fennec.