You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was doing some benchmarking and noticed a memory leak stemming from having uirevision=1. i comment out the field and no more leak.
I can't say if this is isolated to scatter3d, but thats what I was benchmarking.
i hit the issue only in storybook. porting the same code over to codesandbox does not encounter the leak. likewise if i comment out my <Scatter3D/> component from the Render, i do not encounter the leak.
apologies in advance if this is a storybook bug and not a plotly bug.
this is all pretty throwaway code half written with claude so forgive me for messiness!
This is unlikely to be an issue in react-plotly.js per se, if it’s in Plotly code it’s probably in plotly.js. But to investigate that we’d really need to be able to reproduce outside of React
(cc @gvwilson, not sure if you have eyes on this repo)
@alexcjohnson unfortunately i dont have a non-react repro handy. this is a pretty trivial nuisance on my end that i figured i'd report in case there's potential implications in a more production-like setting. so no worries on my end
I was doing some benchmarking and noticed a memory leak stemming from having uirevision=1. i comment out the field and no more leak.
I can't say if this is isolated to scatter3d, but thats what I was benchmarking.
i hit the issue only in storybook. porting the same code over to codesandbox does not encounter the leak. likewise if i comment out my
<Scatter3D/>
component from the Render, i do not encounter the leak.apologies in advance if this is a storybook bug and not a plotly bug.
this is all pretty throwaway code half written with claude so forgive me for messiness!
The text was updated successfully, but these errors were encountered: