991084 - [Buri] Loading CNN website crashes the browser

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Performance, defect, P2)

Description

[No-Jun Park [:njpark]]

STR:

Open firefox browser, and go to cnn.com, and select '5 things to know for your day' link.  the exact link is:
http://newday.blogs.cnn.com/2014/04/02/5-things-to-know-for-your-new-day-wednesday-april-2-2014/?hpt=hp_t2

Wait for it to load.

Expected:
The page loads without issue

Actual:
The browser crashes with "We tried to display this web page, but it's not responding" error while loading images.

Attached is the logcat.

Version:
Gaia      6274b3645b3d41df4aa5a55398b5d106edf1c528
Gecko     https://hg.mozilla.org/mozilla-central/rev/4941a2ac0786
BuildID   20140402040201
Version   31.0a1
ro.build.version.incremental=eng.tclxa.20131223.163538
ro.build.date=Mon Dec 23 16:36:04 CST 2013

Comment 1

[No-Jun Park [:njpark]]

Attachment: logcat when cnn site failed to load

Comment 2

[No-Jun Park [:njpark]]

Hi nical, is this by any chance related to the bug 980647?

Comment 3

[Jason Smith [:jsmith]]

No-Jun - Is there a crash report URL present after you run this STR?

We also need to know if this happens on 1.1 or not, as that will determine if this is a performance regression in gecko or a site problem.

Comment 4

[No-Jun Park [:njpark]]

Just verified that this happens on 1.1 on buri as well.

There is no crash report URL present- all it displays is close tab or reload page.  (the browser itself did not crash)

Comment 5

[Jason Smith [:jsmith]]

Ok - then that's a TE issue.

Comment 6

[Gabriele Svelto [:gsvelto] (PTO)]

Just tested on today's master build, this is an out-of-memory condition. The browser memory usage keeps going up while loading the page triggering multiple low-memory notifications until it completely runs out of memory and gets killed by the LMK. I'll try getting an about:memory report to see where the memory is going and what we can do about it.

Comment 7

[Hallvord R. M. Steen [:hallvors]]

Jason, why is this TE? Shouldn't we look into whether we can fix memory leaks or optimise mem usage?

Comment 8

[Karl Dubost💡 :karlcow]

How the page is performing on other browsers with platform more or less equivalent?

Comment 9

[Jason Smith [:jsmith]]

No-Jun - Is the site loading at the target URL a desktop site or a mobile site?

Comment 10

[No-Jun Park [:njpark]]

The page is optimized for mobile, so it looks like a mobile site.
Shortened URL for easy mobile check: http://cnn.it/QFqKFX

Comment 11

[Jason Smith [:jsmith]]

Okay - so that means this is actually a FxOS bug then.

Comment 12

[No-Jun Park [:njpark]]

Just to note, on my Nexus 4 with Android 4.4, Firefox actually loads this page with no issues.

Comment 13

[Gabriele Svelto [:gsvelto] (PTO)]

Attachment: about:memory after loading the page

I've tried opening the page on my Peak using the current master build as it has enough memory to do it. This is the output of about:memory after the page has finished loading.

From a bird's eye view I'd say the page is pretty large in and by itself but we're also suffering from some significant inefficiencies while loading this page. On ~130 MiB of explicit allocations we have ~7MiB of unused-gc-things and ~8MiB of wasted heap. That's 13% of pure overhead. heap-unclassified is also fairly large at 13+ MiB.

Comment 14

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

There may be some things we can do here but this site really does use a ton of memory.

Comment 15

[Nicholas Nethercote [inactive]]

P3 because the site uses so much memory, so there's no single action we can take that will help this.

Comment 17

[Eric Rahm [:erahm]]

Closing out old Firefox OS specific memshrink bugs.