Closed archerallstars closed 8 months ago
I tried launching my local gphoto2 with:
gphoto2 --stdout --capture-movie | ffmpeg -i - -vcodec rawvideo -pix_fmt yuv420p -threads 2 -f v4l2 /dev/video13
There's no memory leak at all.
Note: my dummy video device is at /dev/video13
which I checked it by v4l2-ctl --list-devices
. I can use my camera through gphoto2 directly. But I would prefer using it through OBS which would provide a lot more options.
The memory leaks message is output by OBS. I doubt it is specific to the gphoto plugin, tho I cannot be 100% certain. It is also unlikely to be specific to the Snap Packaged release of OBS (https://github.com/obsproject/obs-studio/blob/f5be6f5fdd2fe34b18518ecd38030f0768845688/UI/obs-app.cpp#L3068)
Is it possible for you to check a non-snapped version of OBS with the gphoto plugin to see if it occurs only with the Snap Package? If it is reproducible with a copy of OBS that isn't from the Snap Package then you have two options below for further steps:
If it is an issue that is specific to the Snap Package then we can look into further diagnostics to attempt to narrow down why the Snap is different.
Closed via #172, which removes the gPhoto plugin.
What happened?
The app, when using with gphoto2 plugin, will cause a lot of memory leaks (see the last line of terminal output), as shown in the screen recording below:
https://user-images.githubusercontent.com/1403194/185512589-9afd160a-b112-4d8f-9ce8-c7b436029cb1.mp4
What should have happened?
There should be no memory leaks.
Output of
snap info $snap_name
Output of
snap connections $snap_name
Output of
snap version
Relevant log output
Teminal output of app