This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hello,
I'm wondering if there is any memory leaks occuring in the update method. As far as I know, update method is recalled each time an event occured (filter for instance).
So normally, all the variables and dom existing on the update are cleaned and recalled.
I developed a custom visual that takes nearly 440 Mb of RAM, after several manipulations (filtering on dataview mainly) the Ram used keeps rising up ...
is it normal ? Is there any leak in custom visuals ?
thank you,
There's a known issue with memory consumption. New API will resolve this issue (please expect a new release soon).
Important to note that custom visuals should not remove DOM for each update call since it produces memory leaks.
To void removing of DOM you should use D3-enter-update-exit flow or use another library that keeps DOM during modifications.
Ignat Vilesov,
Software Engineer
Microsoft Power BI Custom Visuals
Okey I see, and will the new API solve this problematic of DOM causing memory leaks ? Because I'm using a library called Leaflet, its difficult to keep the same DOMs. since its all about maps.
Yes, it will reduce memory consumption but you should also optimize your code in order not to remove DOM for each update call.
Ignat Vilesov,
Software Engineer
Microsoft Power BI Custom Visuals
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |