-
Notifications
You must be signed in to change notification settings - Fork 53
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 leak with open_video_out #359
Comments
What if you put a gc safepoint in the loop? |
Sorry, I forgot to mention I already tried that. I added Base.GC.gc() to the loop but it didn't have any affect. Maybe "gc safepoint" refers to something else? |
I mean Is the memory still retained after close and a sleep? |
Not sure what exactly you mean by close and sleep, but if I have more than 20 frames in the example above then Julia crashes and the memory is released. If I am careful and use only 20 frames, then the memory isn't released before I exit that Julia session. |
1 similar comment
Not sure what exactly you mean by close and sleep, but if I have more than 20 frames in the example above then Julia crashes and the memory is released. If I am careful and use only 20 frames, then the memory isn't released before I exit that Julia session. |
I see the same and it's freed after close and GC
|
So is this expected? |
I can take a look at this
…On Fri, May 20, 2022, at 07:56, Yakir Luc Gagnon wrote:
So is this expected?
—
Reply to this email directly, view it on GitHub <#359 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABUDZT4CBXX4DTCTDQRKFZLVK6RYZANCNFSM5WPCI4RQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
When encoding a video with large frames, Julia crashes because the system runs out of memory.
I made the following MWE to illustrate this (I stole @yiyuezhuo
get_memory_usage
function from this gist, thank you yiyuezhuo!)which looks like this:
The text was updated successfully, but these errors were encountered: