1218036 - Android: Close without alert when load long pages or script, page recovery not exist

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[Wellington Torrejais da Silva]

User Agent: Mozilla/5.0 (Android 4.4.4; Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
Build ID: 20151020031317
Firefox for Android

Steps to reproduce:

Many times the browser close whiteout any info. Probably because long pages, unresponsive script or high memory usage. Please test on mobile http://acasadasquestoes.com.br/simulados/resolver/H0#.VgCzjYShc_7


Actual results:

Close,  many times. Please implement the recover page. 


Expected results:

Normal use, whiteout crash or choose. And lert before close. And recovery page. Thanks!

Comment 1

[Ryan VanderMeulen [:RyanVM]]

Reproduced a long hang loading the page followed by crashing on both Firefox 41 and Firefox 43. For some reason, the crash reports aren't showing up in about:crashes even though I'm telling it to send them, though.

This page is pretty brutal on desktop Firefox too, though. Got the slow script dialog shortly after loading it. Also takes forever to load on Chrome 46 and Edge (and hangs in the mean time).

Have you been able to successfully submit a crash report? If so, can you please provide the ID for it? Thanks!

Comment 2

[Wellington Torrejais da Silva]

Attachment: tmp_24272-Screenshot_2015-10-28-23-41-16-1650085112.png

I have a lot of crashes

Comment 3

[Wellington Torrejais da Silva]

Attachment: tmp_24272-Screenshot_2015-10-28-23-41-06-605441509.png

Some close not generate crash in about:crashes.

Comment 4

[Wellington Torrejais da Silva]

Attachment: tmp_24272-Screenshot_2015-10-28-23-40-55-731185455.png

Frequent problems after multimedia play

Comment 5

[Wellington Torrejais da Silva]

Attachment: tmp_24272-Screenshot_2015-10-28-23-40-311371245648.png

Ex:
https://crash-stats.mozilla.com/report/index/a6f0298d-3067-4474-ae08-ce30c2151024
And
https://crash-stats.mozilla.com/report/index/31ed2ff6-b55e-4102-b785-ec4b82151026
And 
https://crash-stats.mozilla.com/report/index/e71d1580-5ab5-417e-94fd-adaf62150904
And
https://crash-stats.mozilla.com/report/index/f5579924-fa3a-44cb-914a-3d9d92150621

Comment 6

[Wellington Torrejais da Silva]

Some different crashes and not found  today crashes for unexpected closes

Comment 7

[Ryan VanderMeulen [:RyanVM]]

I have no idea where to put this bug given that the crash stacks appear to be all over the place. Any thoughts, Snorp?

Comment 8

[Wellington Torrejais da Silva]

(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #7)
> I have no idea where to put this bug given that the crash stacks appear to
> be all over the place. Any thoughts, Snorp?

I have no idea too :-/

Comment 9

[James Willcox (:snorp) ([e-mail]) (he/him)]

No idea. Looks like it could be caused by OOM?

Comment 10

[Wellington Torrejais da Silva]

(In reply to James Willcox (:snorp) ([e-mail]) from comment #9)
> No idea. Looks like it could be caused by OOM?

Appears OOM problem, but the report of crashes not was generated.
It's possible to develop protections to OOM ?

Tab closed is better than browser close.

Desktop browser inform problems on page.
But mobile app not inform.

Comment 11

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.