Closed schoebelh closed 3 years ago
Most likely this is a multi-threaded client and XInitThreads has not been called. I cannot reproduce such an error in myself, and I do not yet know how to fix it. I will try.
Am i right that you thought about any of my active plugins as source of crash...?
No it's a GLX problem. Does VDR crash always or sometimes, or after switching from bionic to focal, for example?
Does VDR crash always or sometimes, or after switching from bionic to focal, for example?
VDR crashes always, shortly after starting the service.
I'll clarify just in case. Have you vdr crash, if disable boblight plugin?
I tested now again - the crash is there when i only disable the boblight plugin (after using vdr with enabled boblight plugin and without "-v cuvid" as option for softhddevice) and then just restart vdr with softhddevice and enabled "-v cuvid". When i reboot the system after that i can start vdr without GLX-crashing. Hope this is not too much confusing described...
With -v cuvid, have you crash in both case, with boblight and without it?
No. If i disable the boblight plugin i had to reboot the system to use the plugin (with -v cuvid) without any errors.
My "normal" usage here is WITH boblight-plugin and without the "-v" switch for softhddevice. For testing i just disabled the boblight plugin, switched to "-v cuvid" and restart vdr (without reboot) and THEN i had the crash again.
It seams like you supposed already - the boblight plugin does not like the "-v cuvid" mode :-/
WIthout "-v cuvid" plugin must use VDPAU. With the latest commit, boblight should work with CUVID, but it doesn't seem to be.
Ok. I disable (ppa-purge) the "graphics driver ppa" and use now the "original" ubuntu nvidia driver 450. Now i can start with boblight plugin enabled AND "-v cuvid".
BUT: After some time vdr crashed again...
Nov 26 16:52:40 yavdr vdr: [2795] VNSI: Requesting clients to reload channel list
Nov 26 16:52:44 yavdr vdr[2761]: X Error of failed request: GLXBadContextTag
Nov 26 16:52:44 yavdr vdr[2761]: Major opcode of failed request: 149 (GLX)
Nov 26 16:52:44 yavdr vdr[2761]: Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Nov 26 16:52:44 yavdr vdr[2761]: Serial number of failed request: 32693
Nov 26 16:52:44 yavdr vdr[2761]: Current serial number in output stream: 32694
Nov 26 16:52:45 yavdr kernel: [ 441.383921] softhddev video[2953]: segfault at 559b0000000a ip 00007f50c0accba4 sp 00007f50328f2590 error 4 in libc-2.31.so[7f50c0a59000+178000]
Nov 26 16:52:45 yavdr kernel: [ 441.383937] Code: c9 0f 11 4b 20 48 89 ee 66 48 0f 6e c0 48 83 ce 01 0f 16 44 24 08 48 89 73 08 0f 11 43 10 49 89 2c 24 48 85 d2 74 8f 48 89 d3 <48> 8b 43 08 89 c2 c1 ea 04 83 ea 02 49 8d 54 d7 10 49 39 d5 0f 85
Nov 26 16:52:45 yavdr boblightd[715]: (CClientsHandler::Process) 127.0.0.1:33974 Connection closed
But i see also this crash:
Nov 26 16:55:13 yavdr vdr: message repeated 2 times: [ [3098] VNSI: Requesting clients to reload channel list]
Nov 26 16:55:16 yavdr vdr[3065]: X Error of failed request: GLXBadContextTag
Nov 26 16:55:16 yavdr vdr[3065]: Major opcode of failed request: 149 (GLX)
Nov 26 16:55:16 yavdr vdr[3065]: Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Nov 26 16:55:16 yavdr vdr[3065]: Serial number of failed request: 26462
Nov 26 16:55:16 yavdr vdr[3065]: Current serial number in output stream: 26463
Nov 26 16:55:16 yavdr kernel: [ 592.193132] epg2vdr-update[3089]: segfault at 21 ip 00007f489970ccd4 sp 00007f484bffec30 error 4 in libvdr-epg2vdr.so.2.4.5[7f48996f6000+8c000]
Nov 26 16:55:16 yavdr kernel: [ 592.193140] Code: 8b 5d 48 4c 8b 7c 24 20 48 85 db 0f 84 9d 00 00 00 4c 8d 65 40 eb 13 0f 1f 80 00 00 00 00 49 89 dc 48 8b 5b 10 48 85 db 74 19 <48> 8b 7b 20 4c 89 fe e8 40 be fe ff 85 c0 79 e4 48 8b 5b 18 48 85
Nov 26 16:55:16 yavdr boblightd[715]: (CClientsHandler::Process) 127.0.0.1:34010 Connection closed
Nov 26 16:55:16 yavdr boblightd[715]: (CClientsHandler::RemoveClient) removing 127.0.0.1:34010
Hope it helps. With boblight-plugin disabled it seems to be stable with "-v cuvid".
Try now.
I use the packages from seahawk's repo - and there will be a new version if YOU release a new one... ;-). Do you think the changes are worth releasing a new version or is this to much unstable...?
Seahawk use git, he doesn't wait for releases.
Seahawk use git, he doesn't wait for releases.
You are absolutely right - the changes are available in seahawks ppa since 3 hours :-). I will test and follow up.
After several hours of testing - no more crashes again with -v cuvid AND boblight plugin enabled. Very nice - thank you... !
Environment: Nvidia Driver 455, Ubuntu Focal fully updated. YaVDR ansible with PPA ppa:seahawk1986-hotmail/vdr-2.4.5-patches enabled.
vdr Plugins enabled:
Log with first 'crash':
Full Log: