New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 665377 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Pages at blog.skylined.nl render rediculously slow

Reported by skylined@chromium.org, Nov 15 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0

Steps to reproduce the problem:
1. Visit http://blog.skylined.nl/20161115001.html
2. Go make some coffee
3. Come back, wait for it finish rendering the page.

Added bonus: resize the window, go have dinner.

What is the expected behavior?
Should render fast like all other browsers

What went wrong?
Not sure where the hotspot is. But that should be easy to find out for any developer. If not, try BugId, it can detect high CPU usage and tell you in which function is probably the root cause.
https://github.com/SkyLined/BugId

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 56.0.2919.0 (Official Build) canary (64-bit)  Channel: canary
OS Version: 10.0
Flash Version: 24.0.0.154
 
Labels: -Type-Bug Type-Bug-Regression
Works fine in my Chrome 54 on Windows 7, might be a regression.

Comment 2 by hdodda@chromium.org, Nov 16 2016

Cc: hdodda@chromium.org
Tested on windows 10 using chrome canary M56 #56.0.2919.0 and issue is not reproduced.
The provided URL is rendering fast as all other browsers.

Attached screencast for reference.

Thanks!


665377.mp4
5.6 MB View Download
Labels: M-56
Thank you, I noticed that this issue only affects Chrome if you're running it with page heap enabled. I am assuming this is because the code is allocating and freeing a LOT of small memory blocks in order to render it. This issue should therefore not affect any real world scenario.

I apologize for wasting your time.
Status: WontFix (was: Unconfirmed)
Based on comment #4 we are closing the issue.

Sign in to add a comment