Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreThe FabCon + SQLCon recap series starts April 14th at 8am Pacific. If you’re tracking where AI is going inside Fabric, this first session is a can't miss. Register now
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
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |