Maybe it is related to this one? https://bugs.chromium.org/p/chromium/issues/detail?id=270000

Thanks for filing the issue!

As per comment# 0, we don't have consistent reproducible steps to test and confirm it, hence adding Needs-Feedback label to it.

@Reporter: Could you please provide sample Test file/URL that reproduces the issue, if possible provide screencast of the issue which help in better understanding and further triaging it in better way.

Thanks!

I would love to reproduce it, but I don't know how to do it. I was using the Memory tab a lot to take a bunch Heap Snapshots, and refreshing the app many times, then eventually I noticed the snapshots started reporting something that didn't make sense (the extra objects).

CLosing and re-opening the tab fixed it.

Could a leak inside the engine itself cause the reports to show erroneous objects that actually don't exist in my app?

Is there some way to debug Chrome itself to inspect it's internals next time this happens?

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per comment# 5 from the reporter, requesting someone from the Dev team help in providing further inputs on this issue.

Thanks!

Good idea about screen casting. Next time it happens I'll record the behavior.

Likely 906847. On the latest canary if you select these objects do their retaining paths go though a "WeakMap" object?