munyooi91 / androidpolice

Automatically exported from code.google.com/p/androidpolice
0 stars 2 forks source link

Jank when scrolling in Chrome for Android app #48

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Open androidpolice.com in Chrome for Android on Nexus 5 and or Android One 
for Indonesia devices.
2. After the page is fully loaded, scroll down.
3. UI jank everywhere. Scrolling experience is so slow and stuttery.

What is the expected output? What do you see instead?
Smooth scrolling 60fps all the way down and up again. Old androidpolice.com 
used to have smooth scrolling experience. :)

What operating system are you on?
Android Lollipop 5.1

What is your browser and its version?
Chrome app for Android v40.

Please provide any additional information below.

Original issue reported on code.google.com by charlesa...@gmail.com on 14 Mar 2015 at 9:21

GoogleCodeExporter commented 9 years ago
I was *just* complaining to Joshua (our designer/developer) about the same 
thing. Something is up, and we are making it a priority to figure out wtf is 
going on.

Original comment by archon810 on 14 Mar 2015 at 9:39

GoogleCodeExporter commented 9 years ago
Thanks! I thought you guys forgot to test it out on mobile. Looking forward for 
this, I won't make any more noise here. :D

Original comment by charlesa...@gmail.com on 14 Mar 2015 at 9:44

GoogleCodeExporter commented 9 years ago
Hi Guys,

I noticed everytime I open up androidpolice.com, Chrome RAM usage increases 
significantly like 300-600MB in the cached processed stats. Is this normal?

I tested it out by opening only one tab on facebook.com and then theverge.com, 
each tab not even touch 150MB.

I'm on Nexus 5 running stock Android 5.1. The screenshots were taken using 
Chrome Beta v42, but it's almost the same RAM usage on Chrome Stable v41.

Original comment by charlesa...@gmail.com on 21 Mar 2015 at 12:18

Attachments:

GoogleCodeExporter commented 9 years ago
Looking into this right now. Trying to figure out where the leak is.

Original comment by joshua.j...@gmail.com on 21 Mar 2015 at 1:00

GoogleCodeExporter commented 9 years ago
Is it possible that it's related to 
https://code.google.com/p/chromium/issues/detail?id=467709? 

Original comment by archon810 on 21 Mar 2015 at 5:09

GoogleCodeExporter commented 9 years ago
It could be. :)

I also tested on Firefox 36 with AdBlockPlus addon and found the RAM usage was 
also high around 300MB where only one tab opened which was androidpolice.com. 
Eventhough the ads are blocked, the scrolling performance still lagging. 
Perhaps AdBlockPlus addon only hid it not blocked.

Original comment by charlesa...@gmail.com on 21 Mar 2015 at 6:58

Attachments:

GoogleCodeExporter commented 9 years ago
Just wondering if there are any updates on this problem? Mobile site is now 
unusable for me now.

Original comment by zeo...@gmail.com on 2 Apr 2015 at 1:45

GoogleCodeExporter commented 9 years ago
There is no update at this time, other than expecting the resolution to that 
Chromium ticket as well as waiting for this 
www.androidpolice.com/2015/03/26/google-is-adopting-a-new-standard-to-make-chrom
e-scrolling-less-craptastic/

Original comment by archon810 on 5 Apr 2015 at 8:22

GoogleCodeExporter commented 9 years ago
I concur

This new site is a pain, compared to the líder one.

Sluggish experience

Original comment by rodymac...@gmail.com on 20 Apr 2015 at 8:47

GoogleCodeExporter commented 9 years ago
I agree that the new responsive site on mobile loads very slowly. It took close 
to 30 seconds to load the home page. I'm connected to WiFi on my Verizon Moto X 
running Android 4.4.4.

The biggest problem I can see is that the "News At A Glance" section is all 
white until the very end of the load. Also, I have a feeling that all of the 
social share/tweet/like counts or some other plugins are loading more slowly on 
mobile.

Original comment by alpasc...@gmail.com on 13 May 2015 at 1:51

GoogleCodeExporter commented 9 years ago
The new NaaG experience is almost here. It's the first major issue we're 
resolving. It'll be worth the wait!

Original comment by archon810 on 13 May 2015 at 4:18