-
Notifications
You must be signed in to change notification settings - Fork 9
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
Memory not properly freed between changes an preview refresh #55
Comments
Thanks for reporting. I can reproduce since the commit bfc002e . Could you check if the latest commit helps, especially when using a CUDA filter with fixed size VRAM allocation? |
That does seem to help, I also noticed, that this only happens when |
The bifrost plugin looks good to me without a memory issue. I checked with a clip with big dimensions so that the memory change is evident enough. |
Strange, if I remove BiFrost from my script the memory leak from refreshing basically goes away. |
Just now on another PC I confirmed that VRAM allocated by filters is freed in the release build (6.6). This means filters are correctly freed on F5 refresh. But possibly, due to an unknown issue, the core is not freed. BiFrost is a temporal filter that relies on frame caches, which is managed by the core. Maybe that explains what you found. |
Hmm,.. so it might be a bug in Vapoursynth itself?
I see the RAM usage of vedit increase by ~18MB per refresh. |
If it's merely 18MB then nobody else would think it's a problem.. |
With this script sure, but my initial script it's 450mb per reload, which might be more concerning for most users. ;) |
Replace bifrost with some other stupid temporal filter like the widely despised temporalsoften2. See if it still leaks. It may be one of gazillion filters before or after. |
@myrsloik :
(no gazillion filters before or after)
it does not happen. |
I did miss |
Build latest version from git to test.
Using:
whenever I change something (for example the values of neo_f3kdb.Deband ) and refresh the preview, ram usage increases by ~450MB
The text was updated successfully, but these errors were encountered: