Posted on Jan 9, 2013 by
Happy Horse
What steps will reproduce the problem? 1. Open the inspector profiles tab and see no heap snapshots 2. Close the inspector 2. Run the jsleakcheck 3. Open the inspector profiles tab and see heap snapshot taking up memory in the process.
What is the expected output? What do you see instead? - Expected: same state as seen in #1 (no snapshots) - See: new snapshot for each time the jsleakcheck is run
What version of the product are you using? On what operating system? Linux Chrome M23
Status: New
Labels:
Type-Defect
Priority-Medium