obs is broken (does not open window)

  • Open
  • quality assurance status badge
Details
2 participants
  • Dr. Arne Babenhauserheide
  • Giovanni Biscuolo
Owner
unassigned
Submitted by
Dr. Arne Babenhauserheide
Severity
normal
D
D
Dr. Arne Babenhauserheide wrote on 16 Jul 2023 12:41
(address . bug-guix@gnu.org)
87lefg5e7t.fsf@web.de
Hi,

a few weeks ago obs (Open Broadcast Studio) stopped working for me.

When I run it, it does not show a window, and pressing C-c does not stop
it (I have to kill it with pkill -9 obs).

Console-output:

info: video settings reset:
base resolution: 1920x1080
output resolution: 1280x720
downscale filter: Bicubic
fps: 60/1
format: NV12
YUV mode: Rec. 709/Partial
info: NV12 texture support not available
info: P010 texture support not available
info: Audio monitoring device:
name: Standard
id: default
info: ---------------------------------
warning: Failed to load 'en-US' text for module: 'decklink-captions.so'
warning: Failed to load 'en-US' text for module: 'decklink-output-ui.so'
libDeckLinkAPI.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
warning: A DeckLink iterator could not be created. The DeckLink drivers may not be installed
warning: Failed to initialize module 'decklink.so'
info: [pipewire] No captures available
warning: v4l2loopback not installed, virtual camera disabled
^Cinfo: ==== Shutting down ==================================================

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
-----BEGIN PGP SIGNATURE-----

iQJEBAEBCAAuFiEE801qEjXQSQPNItXAE++NRSQDw+sFAmSzycYQHGFybmVfYmFi
QHdlYi5kZQAKCRAT741FJAPD69cVD/4rvr7pXxeaGm9/gyLVxfjilCuBLGgEstzm
IkODxQxBUjfvWx7Igxm+yOUSF9UcySiMMDVqcOj2sTQAhEHq6n1TOnSeFVPCurlH
WKKvJ+DZnilV/pNRoYkHt9idD29UaxLuYqP7aw9k6TpV8JYeKFKFYXhhc/GrKvIb
M2OlNdBA3iSYYhlyBCfiJ/OmDFbXgwKy1MXGEXAr8ccG/D32JtKd9hjTtkbwpRR4
RCkyJij6LNChQ4XSxJzDn+p79z7vBTSyiMoz4hRnf9bvwFQEv7oHq4CpF+M8z3XN
PLxV94gxAAu84W/Il9Ocgxy16hHZ6zZayrmoxOkxr1FCc3cUEU//U5+u9PYI7o1b
4jxE03vyyMHefubAk1CPV8fUQfZY99/een/nyEwGlAY0nx90HmGLPyIGX201oQPf
G9iNrp51yP5BaIC5kPiujELIvcdbqTV0DL/HPyPq1Bj/f7ga2Qlc3Ip/yEed3fx1
Afvzf7agRdYAO20CtfuHfEaX5We3j/Y+KFAInks/Mh8488ZbCgiMSJIINR3cqf1V
XwtP3mfh0LwKlVxtzvTYFoiOyurMNoH7GJcxmTtnEKfgmpgBaOWdqGUwqXtpyZrE
Gx6zrmo0DhqEy41wQ0Axuujoup3VGlqhimCeT5VPUgYYeRPDofvKhD/zajEU7Dai
pQR52yLRYYjEBAEBCAAuFiEE3Si95tmHXKvOSosd3M8NswvBBUgFAmSzycYQHGFy
bmVfYmFiQHdlYi5kZQAKCRDczw2zC8EFSPKXA/4hPAW8mQi20GZV204/JFFeszvf
iC3YmQKsWEPhuaKQDrxgKcuGIF2I0viiIvLdjZ176I1QFCA+tyREMCjaKCTKsOP4
D6yJhWfoWUuQRbwYF3TwKVycLVl0MS1JKTFa7oaWaMk5mmoxglPu6TCcX+63IqBB
GE35baNFSoTxXdISxQ==
=Jyk8
-----END PGP SIGNATURE-----

D
D
Dr. Arne Babenhauserheide wrote on 22 Jul 2023 06:59
(address . 64663@debbugs.gnu.org)
878rb835dx.fsf@web.de
This problem was resolved for me with the trick from the thread at
help-guix "OBS Studio memory leak":

Robby Zambito <…> writes:

Toggle quote (10 lines)
> Guillaume Le Vaillant <…> writes:
>
>> It looks like an issue with the shader cache of mesa.
>> After clearing it, I don't see the memory leak anymore.
>>
>> Could you try doing a "rm -r $HOME/.cache/mesa_shader_cache/*" and see
>> if it also solves the issue for you?
>
> This worked for me! Thank you!

It also works for me.

Can we somehow automate this solution?

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
-----BEGIN PGP SIGNATURE-----

iQJEBAEBCAAuFiEE801qEjXQSQPNItXAE++NRSQDw+sFAmS7YvoQHGFybmVfYmFi
QHdlYi5kZQAKCRAT741FJAPD6zNOD/98Y5RxL686AvLqfBqyFK4OkebTE5XRqQi2
18DRkrdabk3fejeEr00QXQ7LjqOtA5wCvLMbieimNjH/OZA5ZzaYsUZIFOZ+Hx9J
FE8z9uxKRdg+w7POkA59cGR0eZL3CB8chIdn0LRNxQ3uPwUBi6nq1FoELpzYpJh/
XQhLFT246FdUZBptXNrTC5ff+HCZJeh+B23Sq3PbyNPvRggaBXRR1u6UfxJbouAp
pnFfvymH4lmQbEmDvx1gT9rFlyHdf2sBlioAwaTksvUjBGcnGx7yhHG9Lkvs2PGV
iw0TjbYfXZRS/vL7wpzx1feQLzcSDMLScDHnxbmBlE53+Yplp1BdzsnV2ICY9y1O
MLc9aAryCBCT5BnUKVza7pys1fDAJY3puHYtWjaKfYlwLFHyK8nEwGzWpWj1t111
hf3nja27y37azwjrdBnYLuTMk7p1MWYCio9IpVobqX6Pby8FcEvlW2BeJZ1weWRu
BQNgLr7OdcxxfAIGQcG93NPwejSWdLmE0rjrS9oQRL7YhS3ePXpUiVm15UGIeX40
BswJvZ/Np0QtpxNtmOb5VyhDna6nOwNQIivW0TGTY76ZEfCpWTZu2blUAdO3zLqW
XCCuDsZ6pAiBVn+XILR9rJCy/TRtKQMPCZn9A7yon9kRoWOaBVFm5uwA+Jy9BMWB
fl1TE1/TFIjEBAEBCAAuFiEE3Si95tmHXKvOSosd3M8NswvBBUgFAmS7YvoQHGFy
bmVfYmFiQHdlYi5kZQAKCRDczw2zC8EFSDViA/4oIHkD34gWziNtXmvmTC1dS7ob
DWWt4XdvsKByYMQtALUtbtC83W5n1wPi24eIYhlTTwwBZoC2io/ceXbkLjpVHldP
J8UM8VcbIS/H5PjOwoyUACg6Vwo/iEVxySufnNvRfETA0/1Rr701yJBkg6qIVAFn
V9GcolUPWJM3oObfCg==
=F9Zc
-----END PGP SIGNATURE-----

G
G
Giovanni Biscuolo wrote on 22 Aug 2023 12:13
bug#64663: MESA shader cache makes OBS not running anymore
87v8d7jsgi.fsf@xelera.eu
Hello Arne,

"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:

[...]

Toggle quote (8 lines)
>> Guillaume Le Vaillant <…> writes:
>>
>>> It looks like an issue with the shader cache of mesa.
>>> After clearing it, I don't see the memory leak anymore.
>>>
>>> Could you try doing a "rm -r $HOME/.cache/mesa_shader_cache/*" and see
>>> if it also solves the issue for you?

[...]

Toggle quote (2 lines)
> Can we somehow automate this solution?

This class of issues (cache invalidation) are recurrent and only
upstream can really solve this... or we should have a post-install
action in guix package manager where we program such invalidations when
upgrading, as a _workaround_ (I guess Debian _is_ doing this, for
example)

The "cache invalidation automation via Guix" discussion is something

The bug you are experiencing is very similar (the same?) reported here:

...upstream is still working (?) on the issue:

All in all this (and all cache invalidation) bug is not Guix specific.


Toggle snippet (6 lines)
we should find a way to make Guix users aware of this kind of problems
and possible workarounds they can apply


Best regards, Gio'

--
Giovanni Biscuolo

Xelera IT Infrastructures
-----BEGIN PGP SIGNATURE-----

iQJABAEBCgAqFiEERcxjuFJYydVfNLI5030Op87MORIFAmTkii4MHGdAeGVsZXJh
LmV1AAoJENN9DqfOzDkSyykQAL52dq7N35ljzC6ccLSA6LqK40F1FrIld9HPmjRq
WGOkClHtT4XxEoVTkFn54h2Nu5b4+Qfm8bSBulF7Oughuh72Am7FxaIbU3R05d4+
SO/BORAl8DPW3VIMeiCysRuJKaX4pT+/iYts9Bmsp5c957JRd8HVzoN/6e6N9031
o2vgj25BiNOI6Rq2XJFIFeIQE7Ru7LCSfNlN+SAXu/uRS0vhcSxXRH8vibNQhwMS
tsb5etQu+DYU1v9cNz6kL1B9Fzegfqyyzma1lXuMeyYGfUxg5kCPJus5+0/mD+6k
SFKGI0B1sx+0D1X3wgkusmBR1gJvrf70CgQAeQ96XzPziJq6jFv8GY9XmEc9cc9O
mH/sGb2L6M0ywNubQ+D/iToSKqXws3Ehle1yDIIZKOpHt/RZlbWwxbwyy0dLZANV
WtH65Rcjjk14GR0sOuQyxIROZYd598lEy0TnZBWISJiv9ux4fAKSUanG9JXRCHtS
vAO55ATjE5iFLJIjzakYH08LlwX6jttZ3FkmZABS53NQZSaDPJQnK1dO24zggDe/
J0kBwVbIk2mlnemdIAh70BELLhXhs/muKskvCx6TbKyI0O0fE918xbqAV/3aGzAD
zLCAq6xwGThTzaVVgKmoyonjRi3A5rdUCtAlWK4QY4rD+re3PWjAb6q52i0qSyeh
e+6i
=dtPj
-----END PGP SIGNATURE-----

?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 64663@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 64663
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch