High memory usage #302
thomas-le183
started this conversation in
General
Replies: 1 comment
-
|
@thomas-le183 thank you for reporting this. In fact, snapdom uses several caches to increase capture speed. As you know there are some options to control cache between instances. Theoretically if cache is disabled the memory used between captures should be the same. I will check it maybe is a bug. In the meantime, if you want to help me you can try usong cache full and the other options as well to contrast with cache disabled |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm encountering a severe memory leak that leads to the application crashing when exporting complex nodes. After investigating, it appears that memory is not being released even with cache set to "disabled" and after explicitly removing the captureResult instance.

The attached image shows the memory usage before capturing, after the first capture, and after the second capture — the heap size keeps increasing and never drops, indicating that memory isn't being properly freed.
I really love this library and appreciate all the work behind it. I’d be grateful if you could guide me on how to resolve or work around this issue. Thank you! 🥇
Beta Was this translation helpful? Give feedback.
All reactions