-
Notifications
You must be signed in to change notification settings - Fork 633
plotly + FlexDashboard + Firefox = huge memory consumption #721
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
By adding This must have something to do with the way rmarkdown/pandoc uses data URIs to produce a standalone HTML file... This isn't something I'll have the bandwidth to fix in the coming months, but hopefully someone from the plotly.js crew can help out, since I'm pretty sure any patch we do provide should be native to plotly.js (cc @etpinard @monfera @timelyportfolio) PS. I'm pretty sure this is related to #483 |
Hmm, And apologies for the semi-dupe; I swear I searched before I posted, but not very well, apparently. |
Hi, how do I set that YAML header? where? because you are right, when opening in Firefox an exported Plotly graph (or rpubs uploaded), it uses a plotly base64 encoded library. But when clicking in "Show in new window" (see attached screen), it references a plotly .js library (see second attached figure). And in the former case it consumes huge amounts of memory, while in the second case it works just fine. |
note to self: hoping plotly/plotly.js#1525 fixes this |
This appears to be fixed. |
I ran into a bug today in which any plotly plot in a FlexDashboard viewed in Firefox (locally or remotely) consumes a huge amount of memory—about 2Gb on my machine, regardless of complexity. The same webpage has no noticeable impact on the memory consumption of Chrome or Safari.
An example of a page that will cause the issue for me:
This is with the development version of plotly (4.4.4) updated yesterday from GitHub.
The text was updated successfully, but these errors were encountered: