-
-
Notifications
You must be signed in to change notification settings - Fork 253
CAP: Can't release HW buffer=1 (skipped frame): Cannot allocate memory #268
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
Comments
Specifically this is repeating:
|
It seems this is a problem inside libcamerify. I recommend to address it to its developers. |
I am have the same hardware and having the same issue. Have you found any solution yet? |
Try |
I'm having this problem as well with latest ustreamer from source + libcamerify on Raspbian Bookworm with a Raspberry Pi Camera module 3. Tried the modprobe command but I still get the same errors from (what looks like) libcamerify and ustreamer
|
I think you need to ask about libcamerify here: https://github.com/raspberrypi/libcamera uStreamer works with pure V4L2 and doesn't do anything weird with the kernel API, so if something doesn't work, then the problem is most likely on the libcamerify side. I'm open to suggestions if the bug is on my side, but the logs show that it doesn't look like it. |
I'm getting the following on an RPI zero 2w and camera v3 noir:
Device:
Steps to reproduce:
Do upgrades and install modules
Output:
It seems there is something happening with releasing memory. When I open the stream page I notice the first seconds images are changing, then the module breaks & starts errorring and can't restore itself.
The text was updated successfully, but these errors were encountered: