Aw Snap/OOM when taking a heap snapshot while debugging
Reported by
cyril.fl...@addepar.com,
Feb 17 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. go to www.google.com 2. Put a breakpoint in one of the JS file 3. Reload 4. When you stop on the breakpoint, take a heap snapshot What is the expected behavior? I used that technique many many times before and got my heap snapshot What went wrong? Aw Snap / Out of Memory Did this work before? Yes I don't know, I don't track closely enough nor do it every month. I would say it was working 3 months ago. Chrome version: 56.0.2924.87 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 24.0 r0
,
Feb 17 2017
Tested in chrome stable #56.0.2924.87 and canary #58.0.3015.0 on Mac 10.11.6 , Ubuntu 14.04 & Win 10.0 able to reproduce the issue. Below are the Bisect Details: Bisect Info: ============= Good Build: 52.0.2712.0(Revision - 388092) Bad Build: 52.0.2713.0 (Revision - 388380) You are probably looking for a change made after 388169 (known good), but no later than 388170 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/76ea7af93b5532777ee787fc4f3039ddfa6125d3..7aff51476ff48588879709275a3c363c6114e085 From the CL above, assigning the issue to the concern owner @yukishiino : ------------------ Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner. Review-Url: https://codereview.chromium.org/1858613002
,
May 29 2017
Is this still reproducible? It doesn't reproduce on my environment. If there will be no objection, I'll close this issue as WontFix.
,
May 31 2017
It seems to be fixed.
,
Jun 1 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by ajha@chromium.org
, Feb 17 2017