-
Notifications
You must be signed in to change notification settings - Fork 9
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
Unable to allocate a surface from internal buffer pool #49
Comments
I have this same error. I've made sure vaapi is enabled. Could be we need to set the |
I have tested with all --codec values (auto, avc, hevc, vp8, vp9) on both iGPU and GPU and I still have the same error. |
I tested on another computer with an intel CPU and Iris Xe iGPU, and it works with vaapi drivers installed. I have the same system on both computer. |
I've improved the error messages in latest git, curious to see what you get now. It's also possible (but maybe unlikely) that this was the root cause as #60, which I just pushed a fix for, so please retest. |
Thanks for your answer I just reinstalled wl-screenrec-git, and I still have the same error, but I have one more message before the program exit
Here are some more information if you need them: I have 2 graphics cards :
I tested to run the program on both GPU using the arguments When I try to run wf-recorder with the arg
But when using
If you need more information about my system, just ask, I will try to do my best to answer. I really like the program on my Intel laptop, more than wf-recorder, so it can be pretty cool if it works on my desktop too. |
it seems they don't use dmabuf at all in this situation, which wl-screenrec always uses. This is somewhat related to #15. I think the only option to get wl-screenrec (barring wl-screenrec shm support, which I have little interest in adding as wf-recorder already fits this usecase well) is to drop your display to 8-bit mode instead of 10. |
Ah, you're right, I removed |
Description:
When executing the
wl-screenrec
command, the following error is encountered:Steps to Reproduce:
Executing the
wl-screenrec
command results in the memory allocation error mentioned above.Environment:
Observations:
The error persists across both AUR packages (
wl-screenrec
andwl-screenrec-git
), and the use of the--no-hw
flag did not resolve the issue.The text was updated successfully, but these errors were encountered: