799651 - [e.me] Most e.me apps crash either the homescreen or the webapp when you follow a link from them

Status: RESOLVED DUPLICATE of bug 796750

(Firefox OS Graveyard :: Gaia, defect, P1)

Description

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

## Environment :
Otoro phone, build 2012-10-09 us
Taken from default.xml in b2g-distro: 
* "platform_build" revision= 0d6d050bc37d3167cc82a1885fd7660456bb0f4e
* "gaia" revision= 5f7dbe06490e6b52a356e033f52fb31c0fa0e2d0 
* "releases-mozilla-central" revision= 1f41d3603a035d64c3b1d7c16dba5fd1ce322957
* "gonk-misc" revision= bac8185ab931c9bc868e9bcb9b636620b8032e5e
  
## Repro :
1. swipe to get to e.me
2. select social
3. select snip.it social news
4. click on a link to an article

## Expected :
1. article appears

## Actual :
1. web app crashes, or you get a white screen w/ unresponsiveness, or you get the homescreen crashing

## Note :
1. trying to test more apps for Bug 798700; I find that most e.me webapps have issues when following a link and it launches the browser

Comment 1

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Suspected dup of bug 798980 (or one of its friends).

Comment 2

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Can you be more specific about what "crash" means?

Comment 3

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

Attachment: screenshot

Apparantly it's not a crash in today's build, more of an "application is not loading properly" error message.  See screenshot.

Comment 4

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

10/10/2012 build.

Comment 5

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

It came out in another thread that this is being triggered by a "failure: other" notification from the browser API.

Can we get some more visibility into what that is?

Comment 6

[Ben Francis [:benfrancis]]

Justin recently helped me understand this a little better.

http://hg.mozilla.org/mozilla-central/file/99898ec9976a/dom/browser-element/BrowserElementChild.js#l644 says:

"TODO See nsDocShell::DisplayLoadError for a list of all the error codes (the status param) we should eventually handle here."

I read this to mean that the mozbrowsererror event of type "other" is fired for any of the errors listed at http://mxr.mozilla.org/mozilla-central/source/docshell/base/nsDocShell.cpp#4089 

This large range of different status codes means there are a large range of potential causes for this screen to be displayed by the window manager, basically any HTTP status code that looks like an error will show the same message.

Comment 7

[(inactive after 6/18) Alive Kuo [:alive]]

https://bugzilla.mozilla.org/show_bug.cgi?id=798722 
We have many similiar bugs of this kind.

Comment 8

[(inactive after 6/18) Alive Kuo [:alive]]

IMO we want to show something more than `other` about network problem, I am going to mark this as dup as 796750.