[Webkit-unassigned] [Bug 247984] References to iframes seem do not get garbage collected

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue May 2 04:18:18 PDT 2023


https://bugs.webkit.org/show_bug.cgi?id=247984

--- Comment #18 from Mark Agranat <magranat at yandex-team.ru> ---
(In reply to Chris Dumez from comment #17)
> I have tried the following test case:
> ```
> for (var i = 0; i < 100000; i++) {
>     setTimeout(() => {
>         document.body.appendChild(document.createElement('iframe'));
>         document.querySelector('iframe').remove();
>     }, 0);
> }
> ```
> 
> We do NOT have a leak. I added logging and I see iframes getting destroyed
> (The HTMLIFrameElement destructor is getting called).
> 
> However, it is true that GC is not destroying frames as fast as they are
> constructed. I see the number of HTMLIframeElement instances steadily
> growing (despite some frames getting destroyed along the way).
> 
> Given that this is not a leak, I am not sure what to do on WebCore side. To
> me, this looks like GC not being aggressive enough.

1) Do you know, do apple have own implementation of GC?
2) Maybe it is possible to make the GC mode more aggressive?
3) Are WebContent process receiving a memory pressure in case of HTMLIframeElement instances growing? Is it possible to force garbage collection in such case?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230502/7d4bcb79/attachment.htm>


More information about the webkit-unassigned mailing list