1234652 - Fennec dies on Yoga 3 Pro x86 tablet with no crash report

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[skierpage]

Attachment: Yoga_ffnightly_adb2.log

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20151210084639

Steps to reproduce:

I installed Firefox from the Google Play Store on my new Yoga 3 Pro x86 tablet. Firefox's "about:" screens and simple sites work fine, but if I load a larger web page and load more, scroll, or zoom, then Firefox often exits. E.g., it dies on a pinch-to-zoom gesture on Slashdot.org.


Actual results:

Firefox dies, returning me to Android's home or lock screen. I never see a Firefox or Android crash reporter and there's nothing in about:crashes.

I reported this in https://support.mozilla.org/en-US/questions/1098598#answer-820785
I installed nightly fennec-46.0a1.multi.android-i386.apk and get the same behavior.
I got adb<->Web IDE working and I don't see any useful output in that.
I used `adb log` to get the Android log (attached), and it has 
  I/ActivityManager( 4378): Process org.mozilla.firefox (pid 21884) has died
the last output from process 21884 is
  V/GeckoDynamicToolbarAnimator(21884): Changing animation to immediate jump
  V/GeckoBrowserApp(21884): On pan/zoom stopped, short page: false; atBottomOfLongPage: false



Expected results:

No silent exits :-)  I'm a long-term user of Firefox for Android on my 2013 Moto X without this issue.

Comment 1

[Kevin Brosnan [Ex-Mozilla]]

at the end of the log

D/Telemetry(21884): StopUISession: awesomescreen.1, reason=null
W/System.err(21884): java.io.FileNotFoundException: https://switchboard-server.dev.mozaws.net/v1?uuid=69b1e17c-ae8c-4d6d-bc2d-55e81b473ad1&device=YT3&lang=eng&country=USA&manufacturer=LENOVO&appId=org.mozilla.firefox&version=43.0
W/System.err(21884): 	at com.android.okhttp.internal.http.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:206)
W/System.err(21884): 	at com.android.okhttp.internal.http.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210)
W/System.err(21884): 	at com.android.okhttp.internal.http.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25)
W/System.err(21884): 	at com.keepsafe.switchboard.SwitchBoard.readFromUrlGET(SwitchBoard.java:410)
W/System.err(21884): 	at com.keepsafe.switchboard.SwitchBoard.loadConfig(SwitchBoard.java:176)
W/System.err(21884): 	at com.keepsafe.switchboard.AsyncConfigLoader.doInBackground(AsyncConfigLoader.java:33)
W/System.err(21884): 	at android.os.AsyncTask$2.call(AsyncTask.java:292)
W/System.err(21884): 	at java.util.concurrent.FutureTask.run(FutureTask.java:237)
W/System.err(21884): 	at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
W/System.err(21884): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
W/System.err(21884): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
W/System.err(21884): 	at java.lang.Thread.run(Thread.java:818)
W/System.err(21884): java.lang.NullPointerException: println needs a message
W/System.err(21884): 	at android.util.Log.println_native(Native Method)
W/System.err(21884): 	at android.util.Log.d(Log.java:139)
W/System.err(21884): 	at com.keepsafe.switchboard.SwitchBoard.loadConfig(SwitchBoard.java:176)
W/System.err(21884): 	at com.keepsafe.switchboard.AsyncConfigLoader.doInBackground(AsyncConfigLoader.java:33)
W/System.err(21884): 	at android.os.AsyncTask$2.call(AsyncTask.java:292)
W/System.err(21884): 	at java.util.concurrent.FutureTask.run(FutureTask.java:237)
W/System.err(21884): 	at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
W/System.err(21884): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
W/System.err(21884): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
W/System.err(21884): 	at java.lang.Thread.run(Thread.java:818)

Comment 2

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Looking at the HttpURLConnectionImpl code:

181    // if the requested file does not exist, throw an exception formerly the
182    // Error page from the server was returned if the requested file was
183    // text/html this has changed to return FileNotFoundException for all
184    // file types
185    if (getResponseCode() >= HTTP_BAD_REQUEST) {
186      throw new FileNotFoundException(url.toString());
187    }

http://androidxref.com/4.4.4_r1/xref/external/okhttp/src/main/java/com/squareup/okhttp/internal/http/HttpURLConnectionImpl.java#186

I'm not sure where HTTP_BAD_REQUEST is defined.

Navigating to the given "error" url causes no issues in my desktop browser – perhaps it's a network issue? Should we catch these issues?

Finkle, does the given url look valid?

Comment 3

[Mark Finkle (:mfinkle) (use needinfo?)]

The SwitchBoard exception is a red herring. The code is already in a try/catch:
http://mxr.mozilla.org/mozilla-central/source/mobile/android/thirdparty/com/keepsafe/switchboard/SwitchBoard.java#396

The exception is just dumped to the logcat. The exception was happening because the Mozilla service was down and 404, which causes a FileNotFoundException. The service is back up now, but like I said, it was never the cause of the crash.

Comment 4

[skierpage]

Someone else reported Firefox (and Chrome) crashing on the same device in the Lenovo support forums, https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Poor-browser-performance-and-crashing-on-Yoga-Tab-3-pro/m-p/2235355

Is there anything I can do to help debug this, like run a debug build? Any web guide to using `adb` or other tools to at least identify what Firefox is doing when it exits?  Can I bring the tablet to the Mozilla S.F. office with cookies, coffee, beer?  Without Firefox I've just bought an expensive black mirror.

Comment 5

[Mira Lobontiu (Android QA)]

Hi,

Does this issue still reproduce?

Thank you!

Comment 6

[skierpage]

(In reply to miralobontiu from comment #5)
> Does this issue still reproduce?
Yes.

The Lenovo Yoga 3 Pro is a high-res tablet with an Intel CPU but only 2GB of RAM. It had terrible memory problems (Android 5.1's Developer info showed it spending most time in low or critical memory state), so Firefox was most likely just running out of RAM. Behavior improved when Lenovo finally updated it to Android 6.0, the tablet works OK for browsing now. But I still come across web pages that simply exit Firefox (and work OK in Chrome). Last one I remember is an image-heavy BBC online news story.

Comment 7

[Mira Lobontiu (Android QA)]

Hi,

I have tried to reproduce the issue with Lenovo Yoga Tablet 2 (Android 4.4.2) and Xiaomi Mi Pad 2 (Android 5.0.1), both with x86 architecture, but I was not able to, using the latest Nightly 65.0a1 (2018-12-04). I opened https://m.slashdot.org, https://planet/mozilla.org, and cnn.com, pinched in to zoom, opened different links from those pages, but everything worked as expected.

Can you, please, download the latest Nightly and retry?
Also, can you provide some more exact Steps to reproduce?

Thank you!

Comment 8

[Stefan Deiac]

Due to the lack of additional info, I'll close this issue as Incomplete. If someone can provide more information regarding this issue, please feel free to reopen it, thanks.