-
Notifications
You must be signed in to change notification settings - Fork 119
Memory Leak | Bloom #132
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
maybe related discussion/cause here |
Was there ever a solution created for this issue? I am running into the same issue within my project. |
Not to my knowledge. If you use postprocessing directly it's avoidable though. |
What do you mean by "directly"? |
@max-hans this library (react-postprocessing) is a thin react abstraction over postprocessing. If you use postprocessing API's directly instead of this library you will likely not run into this issue (but will also have to do lifecycle management yourself). |
As described in #68 there's a memory leak when updating the intensity of
Bloom
Here's our reproduction:
https://codesandbox.io/s/mystifying-kare-k4lh3b?file=/src/App.js
Screencast: (Activity Monitor > View > Update Frequency > Very Often (1sec)
The text was updated successfully, but these errors were encountered: