having retainers (possible memoryleak) when rendering multiple root elements
See original GitHub issueHi there
I’m trying out uhtml and i’ve ran into a specific issue (retainers) when rendering multiple root elements like:
html`<div>1</div><div>2</div>
it doesn’t happen when using an enclosed parent like:
html`<div><div>1</div><div>2</div></div>
repro here:
https://github.com/fopsdev/retainers_in_uhtml_rendering
(i’ve also included a mp4 showing how i go after retainers)
Thanks for any enlightment 😃
Issue Analytics
- State:
- Created a year ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Vue memory leak when rendered components are removed
I have tried locating the issue with heap snapshots but it only shows a child component as retainer. I cannot locate what is...
Read more >MemLab: An open source framework for finding JavaScript ...
MemLab traverses the heap and generates retainer traces for each leaked object. A retainer trace is an object reference chain from the GC...
Read more >Temperature check on possible memory leak in Holistic JS ...
Hello! I'm using the Holistic web solution in a WebRTC streaming application. We've occasionally seen Holistic processing crash in a way ...
Read more >Fixing Memory Leaks in AngularJS and other ... - dwmkerr.com
A page it is rendering may no longer need as much memory as it needed before, but that doesn't mean the browser needs...
Read more >4 Types of Memory Leaks in JavaScript and How to Get Rid Of ...
In essence, memory leaks can be defined as memory that is not required by an application anymore that for some reason is not...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
yup, the problem is similar here with “static fragments” when these are referenced, even if the content they hook doesn’t exist anymore … but again, once you have these de-referenced, nothing like that bug should happen.
let’s see. will start porting one of the projects tomorrow so i can compare.