games-on-whales/wolf
1
0
Fork 0
mirror of https://github.com/games-on-whales/wolf.git synced 2026-10-15 21:12:08 +00:00
Code Issues 119 Projects Packages Wiki Activity

[GH-ISSUE #212] Connecting two clients, if one gets stuck and reconnected, it will cause Wolf to crash #143

New issue
Closed
opened 2026-10-15 12:57:06 +00:00 by bsakaguchi · 7 comments
bsakaguchi commented 2026-10-15 12:57:06 +00:00
Owner
Copy link

Originally created by @HeiyuEP on GitHub (Jun 15, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/212

error msg:

wolf-1  | 0:01:35.050454100     1 0xfffeec004250 FIXME                default gstutils.c:4169:gst_element_decorate_stream_id_internal:<interpipesrc3> Creating random stream-id, consider implementing a deterministic way of creating a stream-id
wolf-1  | 07:39:02.679024737 DEBUG | Setting up wolf_udp_sink
wolf-1  | 0:01:36.434361014     1 0xfffeec004250 WARN                 basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc3> segment format mismatched, ignore
wolf-1  | 07:39:04.509221374 DEBUG | [GSTREAMER] Forcing IDR
wolf-1  | 07:39:04.924940071 DEBUG | 139.159.170.22 [GET] HTTP://172.19.0.2/serverinfo
wolf-1  | 07:39:04.974283122 DEBUG | 139.159.170.22 [GET] HTTPS://172.19.0.2/serverinfo
wolf-1  | 07:39:07.993648627 DEBUG | 139.159.170.22 [GET] HTTP://172.19.0.2/serverinfo
wolf-1  | 07:39:08.016592539 DEBUG | 139.159.170.22 [GET] HTTPS://172.19.0.2/serverinfo
wolf-1  | 07:39:11.039167114 DEBUG | 139.159.170.22 [GET] HTTP://172.19.0.2/serverinfo
wolf-1  | 07:39:11.063309769 DEBUG | 139.159.170.22 [GET] HTTPS://172.19.0.2/serverinfo
wolf-1  | 07:39:11.090501822 DEBUG | 139.159.170.22 [GET] HTTPS://172.19.0.2/applist
wolf-1  | 07:39:14.108282683 DEBUG | 139.159.170.22 [GET] HTTP://172.19.0.2/serverinfo
wolf-1  | 07:39:14.136355968 DEBUG | 139.159.170.22 [GET] HTTPS://172.19.0.2/serverinfo
wolf-1  | 07:39:38.115180941 DEBUG | [ENET] disconnected client: 139.159.170.3:28915
wolf-1  | 07:39:38.115251148 DEBUG | [GSTREAMER] Pausing pipeline: 9946410804784563243
wolf-1  | 07:39:38.115275240 DEBUG | [GSTREAMER] Pausing pipeline: 9946410804784563243
wolf-1  | 07:39:38.219191485 DEBUG | 139.159.170.3 [GET] HTTP://172.19.0.2/serverinfo
wolf-1  | 07:39:38.257693413 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/serverinfo
wolf-1  | 07:39:38.286993782 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/applist
wolf-1  | 07:39:41.447978001 DEBUG | 139.159.170.3 [GET] HTTP://172.19.0.2/serverinfo
wolf-1  | 07:39:41.474883775 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/serverinfo
wolf-1  | 07:39:44.500034583 DEBUG | 139.159.170.3 [GET] HTTP://172.19.0.2/serverinfo
wolf-1  | 07:39:44.524636911 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/serverinfo
wolf-1  | 07:39:47.556649867 DEBUG | 139.159.170.3 [GET] HTTP://172.19.0.2/serverinfo
wolf-1  | 07:39:47.582285371 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/serverinfo
wolf-1  | 07:39:48.240068986 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/resume
wolf-1  | 07:39:48.240191738 DEBUG | Host app state folder: /etc/wolf/9946410804784563243/2077-TEST-2, creating paths
wolf-1  | 07:39:48.270283899 DEBUG | [RTSP] found session by matching IP: 139.159.170.3
wolf-1  | 07:39:48.270311402 DEBUG | [RTSP] received command OPTIONS
wolf-1  | 07:39:48.295068970 DEBUG | [RTSP] found session by matching IP: 139.159.170.3
wolf-1  | 07:39:48.295087092 DEBUG | [RTSP] received command DESCRIBE
wolf-1  | 07:39:48.310146949 DEBUG | [RTSP] found session by matching IP: 139.159.170.3
wolf-1  | 07:39:48.310162620 DEBUG | [RTSP] received command SETUP
wolf-1  | 07:39:48.326399270 DEBUG | [RTSP] found session by matching IP: 139.159.170.3
wolf-1  | 07:39:48.326416072 DEBUG | [RTSP] received command SETUP
wolf-1  | 07:39:48.349957604 DEBUG | [RTSP] found session by matching IP: 139.159.170.3
wolf-1  | 07:39:48.349973575 DEBUG | [RTSP] received command SETUP
wolf-1  | 07:39:48.376101785 DEBUG | [RTSP] found session by matching IP: 139.159.170.3
wolf-1  | 07:39:48.376118227 DEBUG | [RTSP] received command ANNOUNCE
wolf-1  | 07:39:48.376218027 DEBUG | [RTSP] Moonlight requested video format HEVC
wolf-1  | 07:39:48.376229288 DEBUG | [RTSP] Adjusted video bitrate to 3068 Kbps
wolf-1  | 07:39:48.391835187 DEBUG | [RTSP] found session by matching IP: 139.159.170.3
wolf-1  | 07:39:48.391851098 DEBUG | [RTSP] received command PLAY
wolf-1  | 07:39:48.401036401 DEBUG | [ENET] connected client: 139.159.170.3:29171
wolf-1  | 07:39:48.401156442 DEBUG | [GSTREAMER] Forcing IDR
**wolf-1  | 07:39:48.904828671 ERROR | Unhandled exception: std::future_error: Promise already satisfied**
wolf-1  | [DLSS-SDK] Set global log level: 4
wolf-1  | 2025-06-15T07:39:48.912389Z ERROR smithay::backend::egl::ffi: [EGL] 0x3006 (BAD_CONTEXT) eglMakeCurrent: EGL_BAD_CONTEXT error: In eglMakeCurrent: Invalid EGLContext (0xfffe3c003741)
wolf-1  |
wolf-1  | 2025-06-15T07:39:48.912403Z ERROR smithay::backend::egl::context: error=`eglMakeCurrent` failed: An EGLContext argument does not name a valid EGL rendering context.
wolf-1  | 2025-06-15T07:39:48.912407Z ERROR waylanddisplaycore::comp: Rendering failed. err=ContextActivationError(MakeCurrentError(BadContext))
wolf-1  | 2025-06-15T07:39:48.912433Z ERROR libgstwaylanddisplay: Rendering error: Pad is EOS
wolf-1  |
wolf-1  | (wolf:1): GStreamer-CRITICAL **: 08:39:48.912: gst_mini_object_unref: assertion 'mini_object != NULL' failed
wolf-1  | 07:39:48.912533421 DEBUG | [WAYLAND] Error during app-src push data
wolf-1  | 2025-06-15T07:39:48.921956Z  WARN smithay::backend::egl::error: Erroneous EGL call didn't set EGLError
wolf-1  | 2025-06-15T07:39:48.921964Z ERROR smithay::backend::egl::context: error=`eglMakeCurrent` failed: An unknown error (0)
wolf-1  | 2025-06-15T07:39:48.921967Z ERROR waylanddisplaycore::comp: Rendering failed. err=ContextActivationError(MakeCurrentError(Unknown(0)))
wolf-1  | 2025-06-15T07:39:48.922014Z ERROR libgstwaylanddisplay: Rendering error: Pad is EOS
wolf-1  |
wolf-1  | (wolf:1): GStreamer-CRITICAL **: 08:39:48.922: gst_mini_object_unref: assertion 'mini_object != NULL' failed
wolf-1  | 07:39:48.922147155 DEBUG | [WAYLAND] Error during app-src push data
wolf-1  | EVP_EncryptInit_ex failed
wolf-1  | EVP_CIPHER_CTX_set_padding failed
wolf-1  | EVP_EncryptInit_ex failed
wolf-1  | EVP_EncryptUpdate failed
wolf-1  | EVP_EncryptFinal_ex failed
wolf-1  | EVP_EncryptInit_ex failed
wolf-1  | EVP_CIPHER_CTX_set_padding failed
wolf-1  | EVP_EncryptInit_ex failed
wolf-1  | EVP_EncryptUpdate failed
wolf-1  | EVP_EncryptFinal_ex failed
wolf-1  | EVP_EncryptInit_ex failed
wolf-1  | EVP_CIPHER_CTX_set_padding failed
wolf-1  | EVP_EncryptInit_ex failed
wolf-1  | EVP_EncryptUpdate failed
wolf-1  | EVP_EncryptFinal_ex failed
wolf-1  | EVP_EncryptInit_ex failed
wolf-1  | EVP_CIPHER_CTX_set_padding failed
wolf-1  | EVP_EncryptInit_ex failed
wolf-1  | EVP_EncryptUpdate failed
wolf-1  | EVP_EncryptFinal_ex failed
wolf-1  | EVP_EncryptInit_ex failed
wolf-1  | EVP_CIPHER_CTX_set_padding failed
wolf-1  | EVP_EncryptInit_ex failed
wolf-1  | EVP_EncryptUpdate failed
wolf-1  | EVP_EncryptFinal_ex failed
wolf-1  | EVP_EncryptInit_ex failed
wolf-1  | EVP_CIPHER_CTX_set_padding failed
wolf-1  | EVP_EncryptInit_ex failed

I obtained the gdb stack at the time of the crash,
stack.txt
The code error occurred in the wait_for_ping function, and handler.unregister cannot return. I am not familiar with the code and cannot understand what happened here.

I'm not sure why the client often gets stuck, and this is a common issue for my computer

Originally created by @HeiyuEP on GitHub (Jun 15, 2025). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/212 error msg: ``` wolf-1 | 0:01:35.050454100 1 0xfffeec004250 FIXME default gstutils.c:4169:gst_element_decorate_stream_id_internal:<interpipesrc3> Creating random stream-id, consider implementing a deterministic way of creating a stream-id wolf-1 | 07:39:02.679024737 DEBUG | Setting up wolf_udp_sink wolf-1 | 0:01:36.434361014 1 0xfffeec004250 WARN basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc3> segment format mismatched, ignore wolf-1 | 07:39:04.509221374 DEBUG | [GSTREAMER] Forcing IDR wolf-1 | 07:39:04.924940071 DEBUG | 139.159.170.22 [GET] HTTP://172.19.0.2/serverinfo wolf-1 | 07:39:04.974283122 DEBUG | 139.159.170.22 [GET] HTTPS://172.19.0.2/serverinfo wolf-1 | 07:39:07.993648627 DEBUG | 139.159.170.22 [GET] HTTP://172.19.0.2/serverinfo wolf-1 | 07:39:08.016592539 DEBUG | 139.159.170.22 [GET] HTTPS://172.19.0.2/serverinfo wolf-1 | 07:39:11.039167114 DEBUG | 139.159.170.22 [GET] HTTP://172.19.0.2/serverinfo wolf-1 | 07:39:11.063309769 DEBUG | 139.159.170.22 [GET] HTTPS://172.19.0.2/serverinfo wolf-1 | 07:39:11.090501822 DEBUG | 139.159.170.22 [GET] HTTPS://172.19.0.2/applist wolf-1 | 07:39:14.108282683 DEBUG | 139.159.170.22 [GET] HTTP://172.19.0.2/serverinfo wolf-1 | 07:39:14.136355968 DEBUG | 139.159.170.22 [GET] HTTPS://172.19.0.2/serverinfo wolf-1 | 07:39:38.115180941 DEBUG | [ENET] disconnected client: 139.159.170.3:28915 wolf-1 | 07:39:38.115251148 DEBUG | [GSTREAMER] Pausing pipeline: 9946410804784563243 wolf-1 | 07:39:38.115275240 DEBUG | [GSTREAMER] Pausing pipeline: 9946410804784563243 wolf-1 | 07:39:38.219191485 DEBUG | 139.159.170.3 [GET] HTTP://172.19.0.2/serverinfo wolf-1 | 07:39:38.257693413 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/serverinfo wolf-1 | 07:39:38.286993782 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/applist wolf-1 | 07:39:41.447978001 DEBUG | 139.159.170.3 [GET] HTTP://172.19.0.2/serverinfo wolf-1 | 07:39:41.474883775 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/serverinfo wolf-1 | 07:39:44.500034583 DEBUG | 139.159.170.3 [GET] HTTP://172.19.0.2/serverinfo wolf-1 | 07:39:44.524636911 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/serverinfo wolf-1 | 07:39:47.556649867 DEBUG | 139.159.170.3 [GET] HTTP://172.19.0.2/serverinfo wolf-1 | 07:39:47.582285371 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/serverinfo wolf-1 | 07:39:48.240068986 DEBUG | 139.159.170.3 [GET] HTTPS://172.19.0.2/resume wolf-1 | 07:39:48.240191738 DEBUG | Host app state folder: /etc/wolf/9946410804784563243/2077-TEST-2, creating paths wolf-1 | 07:39:48.270283899 DEBUG | [RTSP] found session by matching IP: 139.159.170.3 wolf-1 | 07:39:48.270311402 DEBUG | [RTSP] received command OPTIONS wolf-1 | 07:39:48.295068970 DEBUG | [RTSP] found session by matching IP: 139.159.170.3 wolf-1 | 07:39:48.295087092 DEBUG | [RTSP] received command DESCRIBE wolf-1 | 07:39:48.310146949 DEBUG | [RTSP] found session by matching IP: 139.159.170.3 wolf-1 | 07:39:48.310162620 DEBUG | [RTSP] received command SETUP wolf-1 | 07:39:48.326399270 DEBUG | [RTSP] found session by matching IP: 139.159.170.3 wolf-1 | 07:39:48.326416072 DEBUG | [RTSP] received command SETUP wolf-1 | 07:39:48.349957604 DEBUG | [RTSP] found session by matching IP: 139.159.170.3 wolf-1 | 07:39:48.349973575 DEBUG | [RTSP] received command SETUP wolf-1 | 07:39:48.376101785 DEBUG | [RTSP] found session by matching IP: 139.159.170.3 wolf-1 | 07:39:48.376118227 DEBUG | [RTSP] received command ANNOUNCE wolf-1 | 07:39:48.376218027 DEBUG | [RTSP] Moonlight requested video format HEVC wolf-1 | 07:39:48.376229288 DEBUG | [RTSP] Adjusted video bitrate to 3068 Kbps wolf-1 | 07:39:48.391835187 DEBUG | [RTSP] found session by matching IP: 139.159.170.3 wolf-1 | 07:39:48.391851098 DEBUG | [RTSP] received command PLAY wolf-1 | 07:39:48.401036401 DEBUG | [ENET] connected client: 139.159.170.3:29171 wolf-1 | 07:39:48.401156442 DEBUG | [GSTREAMER] Forcing IDR **wolf-1 | 07:39:48.904828671 ERROR | Unhandled exception: std::future_error: Promise already satisfied** wolf-1 | [DLSS-SDK] Set global log level: 4 wolf-1 | 2025-06-15T07:39:48.912389Z ERROR smithay::backend::egl::ffi: [EGL] 0x3006 (BAD_CONTEXT) eglMakeCurrent: EGL_BAD_CONTEXT error: In eglMakeCurrent: Invalid EGLContext (0xfffe3c003741) wolf-1 | wolf-1 | 2025-06-15T07:39:48.912403Z ERROR smithay::backend::egl::context: error=`eglMakeCurrent` failed: An EGLContext argument does not name a valid EGL rendering context. wolf-1 | 2025-06-15T07:39:48.912407Z ERROR waylanddisplaycore::comp: Rendering failed. err=ContextActivationError(MakeCurrentError(BadContext)) wolf-1 | 2025-06-15T07:39:48.912433Z ERROR libgstwaylanddisplay: Rendering error: Pad is EOS wolf-1 | wolf-1 | (wolf:1): GStreamer-CRITICAL **: 08:39:48.912: gst_mini_object_unref: assertion 'mini_object != NULL' failed wolf-1 | 07:39:48.912533421 DEBUG | [WAYLAND] Error during app-src push data wolf-1 | 2025-06-15T07:39:48.921956Z WARN smithay::backend::egl::error: Erroneous EGL call didn't set EGLError wolf-1 | 2025-06-15T07:39:48.921964Z ERROR smithay::backend::egl::context: error=`eglMakeCurrent` failed: An unknown error (0) wolf-1 | 2025-06-15T07:39:48.921967Z ERROR waylanddisplaycore::comp: Rendering failed. err=ContextActivationError(MakeCurrentError(Unknown(0))) wolf-1 | 2025-06-15T07:39:48.922014Z ERROR libgstwaylanddisplay: Rendering error: Pad is EOS wolf-1 | wolf-1 | (wolf:1): GStreamer-CRITICAL **: 08:39:48.922: gst_mini_object_unref: assertion 'mini_object != NULL' failed wolf-1 | 07:39:48.922147155 DEBUG | [WAYLAND] Error during app-src push data wolf-1 | EVP_EncryptInit_ex failed wolf-1 | EVP_CIPHER_CTX_set_padding failed wolf-1 | EVP_EncryptInit_ex failed wolf-1 | EVP_EncryptUpdate failed wolf-1 | EVP_EncryptFinal_ex failed wolf-1 | EVP_EncryptInit_ex failed wolf-1 | EVP_CIPHER_CTX_set_padding failed wolf-1 | EVP_EncryptInit_ex failed wolf-1 | EVP_EncryptUpdate failed wolf-1 | EVP_EncryptFinal_ex failed wolf-1 | EVP_EncryptInit_ex failed wolf-1 | EVP_CIPHER_CTX_set_padding failed wolf-1 | EVP_EncryptInit_ex failed wolf-1 | EVP_EncryptUpdate failed wolf-1 | EVP_EncryptFinal_ex failed wolf-1 | EVP_EncryptInit_ex failed wolf-1 | EVP_CIPHER_CTX_set_padding failed wolf-1 | EVP_EncryptInit_ex failed wolf-1 | EVP_EncryptUpdate failed wolf-1 | EVP_EncryptFinal_ex failed wolf-1 | EVP_EncryptInit_ex failed wolf-1 | EVP_CIPHER_CTX_set_padding failed wolf-1 | EVP_EncryptInit_ex failed wolf-1 | EVP_EncryptUpdate failed wolf-1 | EVP_EncryptFinal_ex failed wolf-1 | EVP_EncryptInit_ex failed wolf-1 | EVP_CIPHER_CTX_set_padding failed wolf-1 | EVP_EncryptInit_ex failed ``` I obtained the gdb stack at the time of the crash, [stack.txt](https://github.com/user-attachments/files/20744463/stack.txt) The code error occurred in the wait_for_ping function, and handler.unregister cannot return. I am not familiar with the code and cannot understand what happened here. I'm not sure why the client often gets stuck, and this is a common issue for my computer
bsakaguchi commented 2026-10-15 12:57:07 +00:00
Author
Owner
Copy link

@HeiyuEP commented on GitHub (Jun 15, 2025):

stack when client stuck.txt

<!-- gh-comment-id:2973598739 --> @HeiyuEP commented on GitHub (Jun 15, 2025): [stack when client stuck.txt](https://github.com/user-attachments/files/20744697/stack.when.client.stuck.txt)
bsakaguchi commented 2026-10-15 12:57:07 +00:00
Author
Owner
Copy link

@ABeltramo commented on GitHub (Jun 15, 2025):

Thanks for the detailed report, I have a few more questions:

  1. Could you please give me a bit more details on what you mean with "client often gets stuck"? Where does it get stuck?
  2. Does the same client work fine when it's the only one connecting or is it always getting stuck?
  3. Which Moonlight client? Can you share a screenshot of the Moonlight stats (CTRL+ALT+SHIFT+S) when the stream works from that client?
  4. And finally, can you share the Wolf debug logs from the very beginning of starting Wolf?

I'm deep in the woods with the zero copy pipeline PR, I'll probably get back to fixing this once I've merged that first, bear with me..

<!-- gh-comment-id:2974652396 --> @ABeltramo commented on GitHub (Jun 15, 2025): Thanks for the detailed report, I have a few more questions: 1. Could you please give me a bit more details on what you mean with "client often gets stuck"? Where does it get stuck? 2. Does the same client work fine when it's the only one connecting or is it always getting stuck? 3. Which Moonlight client? Can you share a screenshot of the Moonlight stats (`CTRL+ALT+SHIFT+S`) when the stream works from that client? 4. And finally, can you share the Wolf debug logs from the very beginning of starting Wolf? I'm deep in the woods with the zero copy pipeline PR, I'll probably get back to fixing this once I've merged that first, bear with me..
bsakaguchi commented 2026-10-15 12:57:07 +00:00
Author
Owner
Copy link

@HeiyuEP commented on GitHub (Jun 16, 2025):

  1. It can get stuck at any time. Sometimes it can play for a long time, and sometimes it gets stuck at the beginning, maybe my network is not very good. When it is stuck, moonlight can no longer operate the game interface, and the status of moonlight is no longer refreshed. I can only quit streaming(CTRL+ALT+SHIFT+Q), but if I reconnect, the other moonlight will not work because wolf crashes.
  2. There are basically no problems when it comes to one moonlight connection(I don't remember if it ever happened, I'm testing one connection now and there is no problem). If we connect two moonlight to wolf, both of them may get stuck(Not sure which one, but there will always be one).

Image
4. I changed some code, complete log is below
Image

wolf-log.txt

<!-- gh-comment-id:2975852615 --> @HeiyuEP commented on GitHub (Jun 16, 2025): 1. It can get stuck at any time. Sometimes it can play for a long time, and sometimes it gets stuck at the beginning, maybe my network is not very good. When it is stuck, moonlight can no longer operate the game interface, and the status of moonlight is no longer refreshed. I can only quit streaming(CTRL+ALT+SHIFT+Q), but if I reconnect, the other moonlight will not work because wolf crashes. 2. There are basically no problems when it comes to one moonlight connection(I don't remember if it ever happened, I'm testing one connection now and there is no problem). If we connect two moonlight to wolf, both of them may get stuck(Not sure which one, but there will always be one). 3. ![Image](https://github.com/user-attachments/assets/d60bc0be-2db6-4d21-ac63-360de48ce622) 4. I changed some code, complete log is below ![Image](https://github.com/user-attachments/assets/be3267e6-2f56-46b3-a9e0-f08330aac36e) [wolf-log.txt](https://github.com/user-attachments/files/20754266/wolf-log.txt)
bsakaguchi commented 2026-10-15 12:57:07 +00:00
Author
Owner
Copy link

@HeiyuEP commented on GitHub (Jun 16, 2025):

I found a client that also triggers this problem, but the probability is lower.

<!-- gh-comment-id:2976315170 --> @HeiyuEP commented on GitHub (Jun 16, 2025): I found a client that also triggers this problem, but the probability is lower.
bsakaguchi commented 2026-10-15 12:57:07 +00:00
Author
Owner
Copy link

@HeiyuEP commented on GitHub (Jun 17, 2025):

I got the gstreamer debug log and found a new discovery. Each call to cudaload3 is followed by cudaconvertscale3, but the last cudaload3 is not followed by cudaconvertscale3 and does not return ok. At the same time, cudaupload4 and cudaconvertscale4 of another pipeline are normal.
The error video pipeline is 12829664931820868236_video

Image

Image

gstreamer_log.txt

<!-- gh-comment-id:2980548085 --> @HeiyuEP commented on GitHub (Jun 17, 2025): I got the gstreamer debug log and found a new discovery. Each call to cudaload3 is followed by cudaconvertscale3, but the last cudaload3 is not followed by cudaconvertscale3 and does not return ok. At the same time, cudaupload4 and cudaconvertscale4 of another pipeline are normal. The error video pipeline is 12829664931820868236_video ![Image](https://github.com/user-attachments/assets/c341c7cc-4aa3-4d73-a393-515e9af02316) ![Image](https://github.com/user-attachments/assets/c26c71bd-ee26-44dc-995e-f1009bb5a91a) [gstreamer_log.txt](https://github.com/user-attachments/files/20776929/gstreamer_log.txt)
bsakaguchi commented 2026-10-15 12:57:07 +00:00
Author
Owner
Copy link

@HeiyuEP commented on GitHub (Jun 19, 2025):

There is no problem with wolf code. It is my PCIE that has a copy problem. A very simple code can also cause this problem.

<!-- gh-comment-id:2988212689 --> @HeiyuEP commented on GitHub (Jun 19, 2025): There is no problem with wolf code. It is my PCIE that has a copy problem. A very simple code can also cause this problem.
bsakaguchi commented 2026-10-15 12:57:07 +00:00
Author
Owner
Copy link

@ABeltramo commented on GitHub (Jun 19, 2025):

@HeiyuEP sorry to hear about that, but I'm kind of glad you've found the actual root cause. I was scratching my head trying to think what could cause your issues in the Wolf codebase over the past few days 😅

<!-- gh-comment-id:2989204499 --> @ABeltramo commented on GitHub (Jun 19, 2025): @HeiyuEP sorry to hear about that, but I'm kind of glad you've found the actual root cause. I was scratching my head trying to think what could cause your issues in the Wolf codebase over the past few days 😅
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
beta
feat/fedora-base-images
stable
axolotlitehotfix/randomly-generated-client-id
feat/vulkan-image
ci/image-smoke-harness
nv12-producer-pin
fix/nvidia-zero-copy
fix/amd-dma-buf-negotiation
fix/joypad-input-leak
codex/party-mode-split-render
ci-fedora-images
test/gst-wld-block-linear
fix/nvidia-blackwell-zero-copy
feat/embed-wolf-den
fix/fake-udev-write-db
fix/session-runner-user
fedora-dockerfile
feat/comprehensive-display-modes
aimee/quickstart-scripts
JBailes-patch-1
dev-nix
dev-fake-uinput
dev-tracy
fix/gst_vaapi
v2024.07
v2023.06
v2023.02
v2022.11
Labels
Clear labels   
🧠 1 - 🤖 999

   
AMD

   
bug

   
bug

   
cannot reproduce

   
documentation

   
duplicate

   
easy

   
enhancement

   
enhancement

   
enhancement

   
fixed?

   
fixed?

   
good first issue

   
hard

   
help wanted

   
Intel

   
invalid

   
LXC

   
medium

   
moonlight-protocol

   
Multi GPU

   
nixos

   
not a bug

   
nvidia

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
wontfix
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
games-on-whales/wolf#143
No description provided.