[Bug] memory leak

[HuaZheLei]

[Bug] memory leak

[Breakthrough]

How many videos are you processing roughly? Does it occur if all of the paths in video_lists are the same video? What OS/environment are you running this under, and how are you running the script?

Thank you.

Edit: I was able to verify on Windows x64 at least on my system there is no memory leak with the code pattern you outlined above, this may be something due to the environment.

[HuaZheLei]

How many videos are you processing roughly? Does it occur if all of the paths in video_lists are the same video? What OS/environment are you running this under, and how are you running the script?

Thank you

Thanks for your reply.

1. I use the script to process 30k videos.
2. If all of the paths in video_lists are the same video, it still occurs.
3. I find this situation on Ubuntu and MacOS.
4. I just use 'python3 xxx.py' in a single thread.

[Breakthrough]

Could you install and try another backend like 'pyav' or 'moviepy'? e.g. run pip install av and open video with video = open_video(video_path, 'pyav')

PySceneDetect is a pure Python library and offloads all video processing to either OpenCV, PyAV, or MoviePy. The next steps would be to narrow down if the memory leak, so trying a different backend will help greatly with that. In the meantime I will setup a VM to test this with locally on Ubuntu.

Can you create and upload a small script that causes the issue? A video clip as well would be helpful to ensure we are testing the same things and I want to see if we can use the exact same script/video. Thanks.

[Breakthrough]

Using the same package versions as you outlined above, on Ubuntu 22.04, I'm running all 3 different backends in a loop the same way you described above. From what I can see memory usage for PySceneDetect+OpenCV and PySceneDetect+MoviePy are steady. As for PyAV, the memory does seem to climb at first, but it is eventually reclaimed and drops again. I don't think PySceneDetect and most of the backends in use have any memory leaks, but am happy to look further into this if you can provide a reproduction.

[wjs018]

I have previously had this issue with moviepy, but that was a couple years ago and I haven't run things in a loop like this since then. I fixed it by writing things out to file occasionally and invoking the del function on a bunch of variables every X number of iterations.

[HuaZheLei]

Using the same package versions as you outlined above, on Ubuntu 22.04, I'm running all 3 different backends in a loop the same way you described above. From what I can see memory usage for PySceneDetect+OpenCV and PySceneDetect+MoviePy are steady. As for PyAV, the memory does seem to climb at first, but it is eventually reclaimed and drops again. I don't think PySceneDetect and most of the backends in use have any memory leaks, but am happy to look further into this if you can provide a reproduction.

Hi, I find that the code uses cv2.VideoCapture to open a video, but without to release it. When I run a for loop, it may cause the memory raising?

[Breakthrough]

Hi, I find that the code uses cv2.VideoCapture to open a video, but without to release it. When I run a for loop, it may cause the memory raising?

The destructor of a VideoCapture object will call release() which applies to Python as well. That will happen automatically at the end of each loop iteration. Are you able to reproduce this with a different versions of OpenCV?

I recently came across https://github.com/bloomberg/memray which might be useful to find the cause. A memory flame graph would be really helpful to identify what part of code is using the memory.

[babyta]

Hello, I recently wrote a synchronous stripping service, and I also have this problem. The free memory keeps decreasing.

[babyta]

‘ scene_manager.detect_scenes ’ Immediately following the previous answer, the execution of splitting will become slower and slower.