-
Notifications
You must be signed in to change notification settings - Fork 61
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
shared screen hangs after a few seconds running #251
Comments
I also replaced the
|
I have exactly the same problem, also using HyperHDR. I will try to also run it with the |
I found this by change...I will try to debug it also, maybe there is a workaround (I suspect the buffer that is holding the last frame must be released immediately in such cases, can be done if it resolves it). If someone is willing to test an experimental amd64 version using a hardware acceleration, it's available here: awawa-dev/HyperHDR#386 (comment) |
I tested it with the @awawa-dev the build won't work on my system, do you have a branch with the changes, then I can compile it myself. |
@Algram I need to clean it and will publish it just after v19 is released, probably month or so. There is one library in this package missing due to the size limit and need to be copied from the standard release but it's mentioned in the thread (ldd will show it). Anyway I will also try it myself. |
Just as an update: This is definitely happening way less often when using the |
@Algram you can build and test this PR awawa-dev/HyperHDR#556 |
I use HyperHDR and its pipewire backend to capture my screen and map it to some LEDs. I realized that after some seconds of using it, nothing is updated anymore and the recorded screen just shows a static frame. However, the mouse is still moving. I validated this using a Jitsi session in Firefox.
Versions and software I use:
While trying to collect data for this bug report I started xdg-desktop-portal-wlr with
-lTRACE
and to my surprise it just does not "crash"/hang any longer. So unfortunately the best I can do is look at the-lDEBUG
log which only prints:This message appears hundreds of times per seconds but doesn't look to suspicious. Let me know if there is any other useful way I can provide you with more data/logs.
The text was updated successfully, but these errors were encountered: