libcamerify causes motion daemon to create zombie processes

[Dale Magee]

Hello,

I was advised to take this issue to the mailing list.

Please see the issue I raised at 
https://github.com/raspberrypi/libcamera/issues/129 and the other issues 
I linked to from there, which descrive the issue I'm having with a bunch 
of detail.

I'm keen to get this resolved as it's causing major system instability 
for me, the entire system becomes unusable when it runs out of memory 
due to this issue.

kbingham commented on the ticket that "Not many people use libcamerify - 
and the more correct route is to use libcamera API's directly, not go 
through libcamerify".

The software I'm trying to use does not support libcamera, so that's not 
an option for me, unfortunately.

Is there some other preferred method to make a raspberry pi camera 3 
show up as a v4l device, and thus able to be used with all the v4l 
software released over the last couple of decades? I've tried searching 
for something like that and all I've come up with is libcamerify, but 
maybe I've missed something?

I see the patch kbingham points me to, but I'm not sure how I'd compile 
and install that on raspbian without causing issues/conflicts with the 
packaged version (e.g if I uninstall libcamera0 with apt, it's going to 
uninstall everything that depends on it, too, right?). Some 
guidance/resources on how to achieve that would be super helpful.

Thanks!