Hello everyone,
I encountered a problem when using the screen recording program. When it was working, the memory usage kept increasing until it filled up the memory, causeing lag. When I stopped recording, the momory was not released and I need to exit the program to solve it. 
1 Like
You might want to report the issue over BeScreenCapture repo, or perhaps @jackburton (its author) can chime in here.
For what it is worth… from a comment on a BeScreenCapture issue…
(on version >= 2.5.2):
[…] It will now hit the disk only after it has exhausted almost all the available memory, so disk shouldn’t be a bottleneck anymore.
So, high memory usage might just be normal and desirable behaviour (except for it ending in lag on the system, of course).
I observed it for a while longer, and found that the program ran out of memory then started using swap space, at which point the system started to slow down.
Thank you, I will move to GitHub.
1 Like
Hi,
it’s fixed in new version 2.9.1.
Should be already available.
Thanks for reporting in the github issue tracker!
8 Likes
I changed it back recently to writing directly on disk because on 32 bit the address space is simply not big enough.
The memory usage should stay low during recording now.
7 Likes
Thank you very much! 