Closed Bug 850176 Opened 7 years ago Closed 4 years ago
[Browser] Browser closes when trying to load certain pages
IN general, I'm experiencing a lot of issues when using the web browser on desktop web pages. I can't tell how common this will be for people in our launch markets, but I'm having issues with just about every relatively complex web page. Often the page load ends with either an error message ("Well, this was embarrassing"), a problem with a script taking too long to respond, or that the entire app closes. Sometimes the entire OS crashes. Here is a video I recorded while browsing on touch.facebook.com and clicking on a link to a page with lots of photos: https://www.youtube.com/watch?v=i1AzTx54sNU The page I was trying to load is this one: http://www.buzzfeed.com/daves4/the-happiest-facts-of-all-time Tested on Unagi running B2G 18.104.22.168-prerelease, build id 20130306070201, update channel beta.
This video shows Facebook being used inside the homescreen wrapper, not the browser app. If a tab crashes or is killed due to low memory in the browser app you are shown the crashed tab screen and given the opportunity to reload the tab. Moving to the homescreen component, but I suspect what you're seeing here is the app (or probably the whole homescreen) being killed by the window manager because the device has run out of memory.
Component: Gaia::Browser → Gaia::Homescreen
Thanks, and yes, you're right, this is the homescreen wrapper. I guess the main point I was trying to make with this report is that for many websites, it's simply not possible to use the current Firefox OS devices for general web browsing due to lack of memory. I'm sure I'm not bringing any news to the table here, but I wanted to file this as this because in my first week of using Firefox OS as my primary phone, this is the biggest issue. There are two aspects of this: 1. Too little memory leads to the majority of the websites I visit impossible to load. And it's not video-heavy sites or anything like that, it's "normal" websites with photos and text, like aftonbladet.se, expressen.se, di.se, most social links on Facebook and Twitter. I don't know if there's a solution to this problem short of putting more memory into the devices, which I assume is not an option for our target price points. 2. When the homescreen wrapper (or browser app) fails due to lack of memory, rather than closing down completely (or showing the crashed tab screen), couldn't it just show a subtle notification that it's out of memory and just stop loading the page, but at least keep the things it managed to load so far? Often what happens is that I'm reading an article on a website, and then after maybe 15 seconds, the homescreen wrapper closes even though what I'm currently staring at is just text. Obviously feel free to dupe, invalid or morph this bug into what makes the most sense. Thanks!
Mass update: Resolve wontfix all issues with legacy homescreens. As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.