Forum Discussion
Memory leaks in Power BI custom visuals
I created this file to reproduce the issue:
https://www.dropbox.com/s/gj3ei0ceav1r229/MemoryLeak-01.pbix?dl=0
Switching back and forth between Page 1 and Page 2 multiple times slow down the entire Power BI window. The CefSharp.BrowserSubprocess.exe increases the memory if you switch between the two pages quickly. If you give time to the page, then CefSharp.BrowserSubprocess.exe releases memory, but it still goes up reaching almost 2GB of virtual memory allocated, and it not always go back to a stable number - waiting more time without actions, memory allocated is released, but I neve see the process going below 1 GB. Considering we have two pages with 30 visuals each, the memory consumption is really high. I agree that there is an improvement, but I still see some problem.
Marco Russo - SQLBI
Hi,
There is a new update to the Oct 2017 release version 2.51.4885.701.
I used Marco's test file and ran a few tests.
1. Increased the number of reports to 4 by duplicating report 2.
2. I can see that between tabbing the reports the memory usage will gradually grow from 870 Mb to ~2Gb
3. Average load time per report increases from ~4 secs to ~12 secs
4. If you tab and wait, the memory usage drops by roughly 30% after about 40 secs of wait time.
5. If you do not wait for the memory collection to kick in, and continue to tab between reports, processor usage tops at 38% and memory about 2.1 Gb. Seems to not go over these limits as with past releases and crash.
Overall, the PBIX file seems stable but is still sluggish in rendering the custom visuals IMO.
Ignat, if we remove all the visuals the memory usage will be minimal, but the dashboard is useless.
It simply doesn't make sense that custom visuals are so expensive.
Requiring to reduce the usage of custom visuals to reduce a memory consumption issue is like saying that it is better to not use custom visuals to avoid problems.
This is not a good message.
Hello mistophiles
Thank you so much for the details.
Ignat Vilesov,
Software Engineer
Microsoft Power BI Custom Visuals
I agree with the observation. Waiting you can see memory released, so the situation is definitely better.
It is still an issue in requiring 2GB to display a couple of report pages. This is a big penalty in many scenarios and I hope MS will do something to address that and to improve custom visual performance and memory requirements.
Marco Russo - SQLBI
Hi Ignat,
Any updates on when will this issue get completely resolved?
Regards,
Ashish
Hi Ignat,
Updates on this will be appreciated as it is impacting our go live date. Customer is not ready to go live with this issue.
Regards,
Ashish
Hello Anonymous
Is that possible to reduce amount of custom visual on the same report page?
That might reduce the memory usage.
Ignat Vilesov,
Software Engineer
Microsoft Power BI Custom Visuals
I'll raise this issue up to PBI CV API team to investigate further.
Ignat Vilesov,
Software Engineer
Microsoft Power BI Custom Visuals
I have the same issue with no custom visuals. Switching tabs accelerates the memory leak until I have to restart the program. This makes drillthrough useless because it relies on tab switching. I'm surprised more people aren't reporting this.
Do you have any updates on this?
This is impacting PowerBI adoption and would definitely be discouraging the developer community from developing custom visuals. Why build something that is known to impact the users?
