possible memory leak with about:blank iframes
Reported by
christop...@gmail.com,
Jul 11
|
||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
Steps to reproduce the problem:
1. Main document:
<iframe id="discardMe" src="someFile.htm"></iframe>
2. Content of someFile.htm:
<html><body><iframe src="about:blank"></iframe></body></html>
3. Main Document:
document.getElementById('discardMe').delete();
4. Check Dev Tools - Frame-Selection
What is the expected behavior?
What went wrong?
The browser keeps the about:blank subframes with every injected extension alive. - Only closing the tab will solve it.
Did this work before? No
Does this work in other browsers? N/A
Chrome version: 67.0.3396.99 Channel: stable
OS Version: 10.0
Flash Version:
I noticed this only with about:blank iframes. Tested with and without extensions enabled.
,
Jul 13
Unable to reproduce the issue on reported chrome version 67.0.3396.99 using Windows 10. Steps: --------- 1. Launched reported chrome 2. As per comment #0 we have created html files and dragged into new tab 3. Opened Dev Tools on - Frame-Selection As we have seen sub-frames alive. @Reporter : It would be really helpful if a sample URL/Test file is provided, so that we can investigate the issue further.If possible also provide expected behavior. Thanks.!
,
Jul 13
I'm also unable to reproduce it with almost plain documents, seems like a problem caused by the website. I'm sorry. Greetings :)
,
Jul 13
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
,
Jul 19
As per comment #3 we are closing this issue as Won't fix. @Reporter: Please feel to raise a new issue if issue is seen in future. Thanks..! |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Jul 12