[V8] Error objects keep hard-reference to the functions on the stack |
||||||||||||
Issue descriptionVersion: 52.0.2738.0 (Official Build) canary (64-bit) - V8 5.2.323 OS: OSX 10.11.4 (15E65) What steps will reproduce the problem? (1) Open the attached HTML file (2) Open the "Developer Tools" (3) Go to the "Profiles" tab (4) Select the "Take Heap Snapshot" and take a heap snapshot (5) Select "Snapshot 1" in the list of snapshots (6) Open "(string)" in the tree (7) Click the string object starting with "BigString..." of about 90MB (8) The "Retainers" panel shows that "myError" is the only object keeping this object alive What is the expected output? The BigString should be garbage collected. There is no way to get a reference to the string using JavaScript code. What do you see instead? The string is not garbage collected. Note: This bug also reproduces in nodejs.
,
May 17 2016
,
May 17 2016
Chrome test, could you please check if this is a new bug or also in 50 already?
,
May 18 2016
Tested the same on mac 10.11 chrome version 52.0.2740.0 and stable version 50.0.2661.102 - The bigString displays "myError" object as shown in the screenshot The issue is observed in win8.1 and Linux as well This can be observed from M43 (43.0.2357.134) builds as well. Hence confirming the issue for further inputs on this.
,
May 18 2016
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 10 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 10 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 11 2017
,
Jul 11 2017
,
Jul 11
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 17
mlippautz please evaluate if this report can be closed or not.
,
Jul 17
This is the combination of two things: - bigStrig gets context-allocated. - the stack trace keeps the functions on the stack alive. |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by ach...@adobe.com
, May 16 2016