711046 - Hang/crash/os reboot after quitting Fennec and reopening

Status: RESOLVED INCOMPLETE

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

Description

[Martijn Wargers (dead)]

This is a follow-up from bug 708291 (which I will mark wfm shortly)
See catlog of the hang here
https://bugzilla.mozilla.org/attachment.cgi?id=581716

Steps to reproduce:
- Open Fennec Native
- Quite Fennec Native
- Open Fennec Native
- Open a New Tab, then load a site

Result:
Fennec closes (crashes? crash reporter doesn't come up at least), the whole Android OS slows down to a crawl, becoming unusable. I have to restart the phone to have it become usable again.

Not sure if the attached logcat is useful, ddms just shut down after a while I guess because the Android OS on the phone was hanging?
If you need another/better logcat, let me know and I'll try.

Comment 1

[Martijn Wargers (dead)]

The steps to reproduce in comment 0 are just one way of reproducing this. Sometimes, just some browsing for one minute or so is also enough for me to trigger the Android OS hang, having to pull out and back in the battery.

It makes it very difficult to test Native Fennec on the LG Optimus Black (sorry, forgot to mention that), so for me, this is a blocker. Using Android version 2.2.2 on that phone.

Comment 2

[Martijn Wargers (dead)]

Often, before the hang, I notice that the page gets blocky/not painted right anymore. Soon afterwards, I get an Android dialog saying "Sorry! Activity Nightly (in application Nightly) is not responding - Force close/Wait".
After I tap on the "Force close" button, the dialog doesn't go away, but stays there and the whole Android OS is frozen. That's when I pull out and then put back in the battery of the phone to restart it (otherwise, it would reboot itself after 5 minutes or so).

Let me know if you need more info or if I should try out stuff.

Comment 3

[Brad Lassey [:blassey] (use needinfo?)]

logcat please

Comment 4

[Martijn Wargers (dead)]

See comment 0, there is a link to a logcat file: https://bugzilla.mozilla.org/attachment.cgi?id=581716
Let me know if that is useful.

Comment 5

[Martijn Wargers (dead)]

Here a video of the hang/crash in action:
http://www.youtube.com/watch?v=d3758QyO2gg&feature=youtu.be

Comment 6

[Martijn Wargers (dead)]

That was a video, where it happened after 3 minutes of browsing or so, but it also happens a lot within one minute of browsing with only 1 tab open.
As I've said before, it makes Native Fennec unusable on the LG Optimus Black. XUL Fennec doesn't seem to have that problem.

Comment 7

[Martijn Wargers (dead)]

Cristian, do you have an LG Optimus Black or 2X? Can you reproduce this issue?

Comment 8

[Stefan Fleiter (:sfleiter)]

Same error for me.
If I can be of any help please do not hesitate to ask.
Also LG Optimus Black Android 2.2.2, software version LG-P970-V10c.

Comment 9

[Martijn Wargers (dead)]

I just noticed I got a similar hang when viewing a large image from a desktop wallpaper site.

Comment 10

[Martijn Wargers (dead)]

It seems that I get these hangs not as easily anymore, so for testing, I can use the LG Optimus Black now, but for regular users, it's a terrible experience to encounter this.

Comment 11

[Erin Lancaster [:elan]]

Martijn: 

Are you still seeing this at all? Can you focus trying to repro on Fx11?

Comment 12

[Martijn Wargers (dead)]

Attachment: testcase

I can still reproduce this on trunk And Fennec11 Aurora.
It seems I could easier reproduce it while opening this testcase in 2 tabs, then having http://nu.nl open and http://slashdot.org open.

Comment 13

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I can't reproduce this issue on a Samsung Galaxy S II... maybe it might be a slower device issue or a 2.2 issue?

Comment 14

[Martijn Wargers (dead)]

I have filed bug 721383, it's also about a Fennec hang, but there I have something very easily reproducable. It might be related to this bug, I don't know.
I'll try to find a regression range with that testcase there.

Comment 15

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

That comes to remind me, I noticed a weird occurrence when using the quit menu and then going to the settings -> application -> nightly.  Sometimes the process will not necessarily stop by the time you are there.  

It also happens with other applications that have a quit in the menu.  I think it might be an android os issue.

Comment 16

[Martijn Wargers (dead)]

This bug isn't useful anymore.