Skip to content
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.

[Bug]: Detached Dom Nodes memory leaks #8756

Open
DanielBelmes opened this issue Sep 12, 2023 · 2 comments
Open

[Bug]: Detached Dom Nodes memory leaks #8756

DanielBelmes opened this issue Sep 12, 2023 · 2 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@DanielBelmes
Copy link
Contributor

Utilizing memlab and memory profiling I have detected a memory leak.

First image is a memory sanpshot of a refresh memory snapshot. The second snapshot is from a 10 min ran tab. Shown in the second is the specifics for the detached dom node.
image
image

@DanielBelmes DanielBelmes added this to the Tech Debt milestone Sep 12, 2023
@DanielBelmes DanielBelmes self-assigned this Sep 12, 2023
@DanielBelmes
Copy link
Contributor Author

@speigg @HexaField Pointing this in your direction as I'm unfamiliar with the Layers. There are other detached dom nodes here to check out as well.

@HexaField
Copy link
Member

Anything regarding XRUI (WebContainer3D, WebLayer) runs in a shadow DOM, I dont know how that affects what is displayed here, either way it worth investigating.

We also have a lot of video & audio nodes that are likely detatched, which is fine.

@DanielBelmes DanielBelmes added the bug Something isn't working label Nov 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants