Issue metadata
Sign in to add a comment
|
Tab becomes unresponsive in 5-10 minutes due to sudden memory leak.
Reported by
skarpinc...@soasta.com,
May 9 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36 Steps to reproduce the problem: 1. Open this link: https://rum-dev.soasta.com/concerto/DashboardServlet?dashboardID=34488901&public=true&filterUID=4c9ea095-7adf-473f-8b27-e237b43bacb8 2. Wait for 5 to 10 minutes. 3. CPU usage becomes around 95-99%. Memory usage by tab starts to suddenly grow. Page becomes unresponsive. What is the expected behavior? Page should stay responsive all time. Memory usage by that page should be in 90-150 MB range. What went wrong? After upgrading to the latest Chrome on Windows 7 most of the dashboards in our product started crashing due to memory leak. Here is the link to one of the pages: https://rum-dev.soasta.com/concerto/DashboardServlet?dashboardID=34488901&public=true&filterUID=4c9ea095-7adf-473f-8b27-e237b43bacb8 Did this work before? Yes I have been working for more than 2 years with no such issues. Chrome version: 50.0.2661.94 Channel: stable OS Version: Windows 7 64-bit Flash Version: Shockwave Flash 21.0 r0 Issue is reproducible only in the latest Chrome on Windows system. Page still works fine in Version 49.0.2579.0 (64-bit) of Chrome Also we have recently noticed the issue like this: ColorTools.colorFadeMultipleGradients( [{stopPercentage:0, color:startColor}, {stopPercentage:1, color:endColor}], percentage); ColorTools.colorFadeMultipleGradients = function(gradientStops, percentage) { The value of "gradientStops[0].stopPercentage" and "gradientStops[1].stopPercentage" becomes very low (like: 1.645184998603488e-204) at some point of time when "ColorTools.colorFadeMultipleGradients()" gets called big number of times ( > 1000 times). }
,
May 9 2016
,
May 10 2016
I was lucky to pause right at the beginning of a leak. And here is what I see. The "current_tick" value becomes corrupted at some point. Btw, the code of the library which the snippet from the screenshot belongs to has not changed lately.
,
May 10 2016
Thank you for providing more feedback. Adding requester "manoranjanr@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 11 2016
Seems like "GL_Renderer" info is missing from the above attachment. Can you please let me know that?? Thank you!
,
May 11 2016
Here is the gpu info from another Windows machine where the issue is also reproducible.
Btw, I've found a workaround for now to avoid the bug. If I force min and max values to be boxed everything works fine.
I'm did this:
var padding = {
min: Number(0),
max: Number(0)
};
instead of:
var padding = {
min: 0,
max: 0
};
Hope it will somehow help.
,
May 12 2016
Thank you for providing more feedback. Adding requester "manoranjanr@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 20 2016
Unable to reproduce the issue on windows 7 using chrome version 50.0.2661.102 and canary 52.0.2742.0.Not observed any freeze with the URL.Able to click the links on the tab after 10 minutes. Please find the attached screen cast and confirm anything missed here. Request you please once try the issue by upgrading chrome to latest stable and update the thread if the issue still persists. Thanks,
,
May 23 2016
Hi, Unfortunately, You won't be able to reproduce the issue any more by hitting that link. Because we had to patch all our servers with the temporary fix I explained in "Comment 6".
,
May 24 2016
Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 25 2016
Thanks for the feedback. Closing this issue as per comment #10. Please feel free to raise a new issue if you see any issue on chrome. Thanks, |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, May 9 2016