-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
releasing Frame object #1152
Comments
Yes, there is no way to deallocate them manually. But we should probably
allow users to do that instead of relying on the garbage collector.
|
so you mean there is no way to free them?
is this useful? |
Yes, that should free them, but there are no guarantees and it affects
performance.
|
…cation with `PointerScope` (issue #1152)
With the changes in commit 924f1d9, we can now control the deallocation of frames using a Let me know if you encounter any problems with this! Thanks |
Hey Thnak you so much for resolving this, it was a big relief for me |
hey i am still facing the memory leak issue, although memoory leak decreased but i am still facing the issues |
@gudduIgn You'll need to provide some details about what you're doing if you expect someone to help! |
The changes have been released as part of JavaCV 1.5. Thanks for reporting and enjoy! |
…cation with `PointerScope` (issue bytedeco#1152)
BTW, I think I've fixed all the memory leaks occurring in |
Hi, Actually I have question.
for some reasons I want to keep an array of Frame objects. I use FFmpegFrameGrabber for extracting gif frames. and I call frame.clone to keep the original Frame.
I want to know when I am done , how can I release that Frame Objects?
is it correct just to assign each element of Frame[] to null ?
The text was updated successfully, but these errors were encountered: