[GH-ISSUE #504] Wolf G_IS_OBJECT critical failure #307

Closed
opened 2026-10-15 12:59:31 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @r0b0tb4c0n on GitHub (Sep 17, 2026).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/504

when i make a connection with moonlight and then press the x in the top right corner, make a second connection pressing the x again, when i try to connect a third time i get the following:

wolf  | 17:40:20.988723740 DEBUG | Setting up wolf_udp_sink
wolf  | 0:00:53.535381756   165 0x7f375815ca80 WARN                basesink gstbasesink.c:1248:gst_base_sink_query_latency:<10907566951849915040_video> warning: Pipeline construction is invalid, please add queues.
wolf  | 0:00:53.535387316   165 0x7f375815ca80 WARN                basesink gstbasesink.c:1248:gst_base_sink_query_latency:<10907566951849915040_video> warning: Not enough buffering available for  the processing deadline of 0:00:00.020000000, add enough queues to buffer  0:00:00.020000000 additional data. Shortening processing latency to 0:00:00.000000000.
wolf  | 17:40:20.997562862 DEBUG | Context already set, passing it to the pipeline.
wolf  |
wolf  | (wolf:165): GLib-GObject-CRITICAL **: 18:40:20.997: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
wolf  |
wolf  | (wolf:165): GLib-GObject-CRITICAL **: 18:40:20.997: g_object_get: assertion 'G_IS_OBJECT (object)' failed
wolf  | 17:40:20.997623065 DEBUG | Wayland source message: WAYLAND_DISPLAY = wayland-2
wolf  | 17:40:20.997630619 INFO  | Wayland display ready, listening on: wayland-2
wolf  | 17:40:20.997745875 DEBUG | [STREAM_SESSION] Start runner
wolf  |
wolf  | (wolf:165): GStreamer-Cuda-CRITICAL **: 18:40:21.001: GstBufferPool* gst_cuda_buffer_pool_new(GstCudaContext*): assertion 'GST_IS_CUDA_CONTEXT (context)' failed
wolf  | 2026-09-17T17:40:21.001984Z  WARN gstwaylanddisplaysrc::waylandsrc::imp: Failed to create CUDA buffer pool: Failed to create CUDA buffer pool
wolf  | 17:40:21.002589767 DEBUG | /dev/dri/renderD129 vendor: NVIDIA Corporation
wolf  | 17:40:21.002606117 INFO  | Mounting nvidia driver nvidia-driver-vol:/usr/nvidia
wolf  | 17:40:21.002640301 DEBUG | [DOCKER] Using fake-udev, creating /etc/wolf/10907566951849915040/Wolf UI/udev/data
wolf  |
wolf  | (wolf:165): GStreamer-Cuda-CRITICAL **: 18:40:21.003: gboolean gst_cuda_context_push(GstCudaContext*): assertion 'ctx' failed
wolf  |
wolf  | thread '<unnamed>' (253) panicked at wayland-display-core/src/utils/allocator/mod.rs:182:26:
wolf  | Failed to create CUDA image from EGLImage: "Failed to push CUDA context"
wolf  | stack backtrace:
wolf  |    0:     0x7f37bc5a844a - <<std[52919eca6bce4da3]::sys::backtrace::BacktraceLock>::print::DisplayBacktrace as core[18c8dd30382e7099]::fmt::Display>::fmt
wolf  |    1:     0x7f37bc5be91a - core[18c8dd30382e7099]::fmt::write
wolf  |    2:     0x7f37bc5ad092 - <std[52919eca6bce4da3]::sys::stdio::unix::Stderr as std[52919eca6bce4da3]::io::Write>::write_fmt
wolf  |    3:     0x7f37bc5913ef - std[52919eca6bce4da3]::panicking::default_hook::{closure#0}
wolf  |    4:     0x7f37bc5a3101 - std[52919eca6bce4da3]::panicking::default_hook
wolf  |    5:     0x7f37bc5a32bb - std[52919eca6bce4da3]::panicking::panic_with_hook
wolf  | 17:40:21.006436068 DEBUG | /dev/dri/renderD129 vendor: NVIDIA Corporation
wolf  |    6:     0x7f37bc5914a8 - std[52919eca6bce4da3]::panicking::panic_handler::{closure#0}
wolf  |    7:     0x7f37bc586839 - std[52919eca6bce4da3]::sys::backtrace::__rust_end_short_backtrace::<std[52919eca6bce4da3]::panicking::panic_handler::{closure#0}, !>
wolf  |    8:     0x7f37bc591d9d - __rustc[8068f81614cfe5c]::rust_begin_unwind
wolf  |    9:     0x7f37bc5bf03c - core[18c8dd30382e7099]::panicking::panic_fmt
wolf  |   10:     0x7f37bc5bee12 - core[18c8dd30382e7099]::result::unwrap_failed
wolf  |   11:     0x7f37bc43ff3f - waylanddisplaycore::utils::allocator::GsCUDABuf::new::h2eafdd9a8f4f4fd0
wolf  |   12:     0x7f37bc3d312d - waylanddisplaycore::comp::apply_video_info::hf928d1399c9232a2
wolf  |   13:     0x7f37bc40929b - <core::cell::RefCell<calloop::sources::DispatcherInner<S,F>> as calloop::sources::EventDispatcher<Data>>::process_events::{{closure}}17:40:21.006548459 DEBUG | [DOCKER] Setting DeviceCgroupRules for hidraw:243 and input:13
wolf  | ::hf5eae17e65b9dc08
wolf  | 17:40:21.006577713 DEBUG | [DOCKER] Container options: {"HostConfig":{"IpcMode":"host","CapAdd":["NET_RAW","MKNOD","NET_ADMIN","SYS_ADMIN","SYS_NICE"],"Privileged":false,"DeviceCgroupRules":["c 243:* rwm","c 13:* rwm"]}}
wolf  |   14:     0x7f37bc41f12a - <calloop::sources::generic::Generic<F,E> as calloop::sources::EventSource>::process_events::h8c0b426af21e4a5c
wolf  |   15:     0x7f37bc3cfa14 - <calloop::sources::channel::Channel<T> as calloop::sources::EventSource>::process_events::h3a544d1cfeb60d35
wolf  |   16:     0x7f37bc3ea811 - <core::cell::RefCell<calloop::sources::DispatcherInner<S,F>> as calloop::sources::EventDispatcher<Data>>::process_events::h76a6e61143c36f2f
wolf  |   17:     0x7f37bc3efa5f - calloop::loop_logic::EventLoop<Data>::run::h5ff07b4030753187
wolf  |   18:     0x7f37bc3d5d9f - waylanddisplaycore::comp::init::hd4a7ecb59f31fa20
wolf  |   19:     0x7f37bc3ebebc - std::sys::backtrace::__rust_begin_short_backtrace::h7eb3c69899e21f7b
wolf  |   20:     0x7f37bc4003b2 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h99ab421c2966aafd
wolf  |   21:     0x7f37bc5a79df - <std[52919eca6bce4da3]::sys::thread::unix::Thread>::new::thread_start
wolf  |   22:     0x7f37cbae57f1 - <unknown>
wolf  |   23:     0x7f37cbb76944 - __clone

and am no longer able to connect after that until i restart wolf.

attached are the debug logs for each connection

connection3.log
connection2.log
connection1.log

the error does not happen if i just use ctrl-alt-shift-q and then reconnect later

Originally created by @r0b0tb4c0n on GitHub (Sep 17, 2026). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/504 when i make a connection with moonlight and then press the x in the top right corner, make a second connection pressing the x again, when i try to connect a third time i get the following: ``` wolf | 17:40:20.988723740 DEBUG | Setting up wolf_udp_sink wolf | 0:00:53.535381756 165 0x7f375815ca80 WARN basesink gstbasesink.c:1248:gst_base_sink_query_latency:<10907566951849915040_video> warning: Pipeline construction is invalid, please add queues. wolf | 0:00:53.535387316 165 0x7f375815ca80 WARN basesink gstbasesink.c:1248:gst_base_sink_query_latency:<10907566951849915040_video> warning: Not enough buffering available for the processing deadline of 0:00:00.020000000, add enough queues to buffer 0:00:00.020000000 additional data. Shortening processing latency to 0:00:00.000000000. wolf | 17:40:20.997562862 DEBUG | Context already set, passing it to the pipeline. wolf | wolf | (wolf:165): GLib-GObject-CRITICAL **: 18:40:20.997: g_object_ref: assertion 'G_IS_OBJECT (object)' failed wolf | wolf | (wolf:165): GLib-GObject-CRITICAL **: 18:40:20.997: g_object_get: assertion 'G_IS_OBJECT (object)' failed wolf | 17:40:20.997623065 DEBUG | Wayland source message: WAYLAND_DISPLAY = wayland-2 wolf | 17:40:20.997630619 INFO | Wayland display ready, listening on: wayland-2 wolf | 17:40:20.997745875 DEBUG | [STREAM_SESSION] Start runner wolf | wolf | (wolf:165): GStreamer-Cuda-CRITICAL **: 18:40:21.001: GstBufferPool* gst_cuda_buffer_pool_new(GstCudaContext*): assertion 'GST_IS_CUDA_CONTEXT (context)' failed wolf | 2026-09-17T17:40:21.001984Z WARN gstwaylanddisplaysrc::waylandsrc::imp: Failed to create CUDA buffer pool: Failed to create CUDA buffer pool wolf | 17:40:21.002589767 DEBUG | /dev/dri/renderD129 vendor: NVIDIA Corporation wolf | 17:40:21.002606117 INFO | Mounting nvidia driver nvidia-driver-vol:/usr/nvidia wolf | 17:40:21.002640301 DEBUG | [DOCKER] Using fake-udev, creating /etc/wolf/10907566951849915040/Wolf UI/udev/data wolf | wolf | (wolf:165): GStreamer-Cuda-CRITICAL **: 18:40:21.003: gboolean gst_cuda_context_push(GstCudaContext*): assertion 'ctx' failed wolf | wolf | thread '<unnamed>' (253) panicked at wayland-display-core/src/utils/allocator/mod.rs:182:26: wolf | Failed to create CUDA image from EGLImage: "Failed to push CUDA context" wolf | stack backtrace: wolf | 0: 0x7f37bc5a844a - <<std[52919eca6bce4da3]::sys::backtrace::BacktraceLock>::print::DisplayBacktrace as core[18c8dd30382e7099]::fmt::Display>::fmt wolf | 1: 0x7f37bc5be91a - core[18c8dd30382e7099]::fmt::write wolf | 2: 0x7f37bc5ad092 - <std[52919eca6bce4da3]::sys::stdio::unix::Stderr as std[52919eca6bce4da3]::io::Write>::write_fmt wolf | 3: 0x7f37bc5913ef - std[52919eca6bce4da3]::panicking::default_hook::{closure#0} wolf | 4: 0x7f37bc5a3101 - std[52919eca6bce4da3]::panicking::default_hook wolf | 5: 0x7f37bc5a32bb - std[52919eca6bce4da3]::panicking::panic_with_hook wolf | 17:40:21.006436068 DEBUG | /dev/dri/renderD129 vendor: NVIDIA Corporation wolf | 6: 0x7f37bc5914a8 - std[52919eca6bce4da3]::panicking::panic_handler::{closure#0} wolf | 7: 0x7f37bc586839 - std[52919eca6bce4da3]::sys::backtrace::__rust_end_short_backtrace::<std[52919eca6bce4da3]::panicking::panic_handler::{closure#0}, !> wolf | 8: 0x7f37bc591d9d - __rustc[8068f81614cfe5c]::rust_begin_unwind wolf | 9: 0x7f37bc5bf03c - core[18c8dd30382e7099]::panicking::panic_fmt wolf | 10: 0x7f37bc5bee12 - core[18c8dd30382e7099]::result::unwrap_failed wolf | 11: 0x7f37bc43ff3f - waylanddisplaycore::utils::allocator::GsCUDABuf::new::h2eafdd9a8f4f4fd0 wolf | 12: 0x7f37bc3d312d - waylanddisplaycore::comp::apply_video_info::hf928d1399c9232a2 wolf | 13: 0x7f37bc40929b - <core::cell::RefCell<calloop::sources::DispatcherInner<S,F>> as calloop::sources::EventDispatcher<Data>>::process_events::{{closure}}17:40:21.006548459 DEBUG | [DOCKER] Setting DeviceCgroupRules for hidraw:243 and input:13 wolf | ::hf5eae17e65b9dc08 wolf | 17:40:21.006577713 DEBUG | [DOCKER] Container options: {"HostConfig":{"IpcMode":"host","CapAdd":["NET_RAW","MKNOD","NET_ADMIN","SYS_ADMIN","SYS_NICE"],"Privileged":false,"DeviceCgroupRules":["c 243:* rwm","c 13:* rwm"]}} wolf | 14: 0x7f37bc41f12a - <calloop::sources::generic::Generic<F,E> as calloop::sources::EventSource>::process_events::h8c0b426af21e4a5c wolf | 15: 0x7f37bc3cfa14 - <calloop::sources::channel::Channel<T> as calloop::sources::EventSource>::process_events::h3a544d1cfeb60d35 wolf | 16: 0x7f37bc3ea811 - <core::cell::RefCell<calloop::sources::DispatcherInner<S,F>> as calloop::sources::EventDispatcher<Data>>::process_events::h76a6e61143c36f2f wolf | 17: 0x7f37bc3efa5f - calloop::loop_logic::EventLoop<Data>::run::h5ff07b4030753187 wolf | 18: 0x7f37bc3d5d9f - waylanddisplaycore::comp::init::hd4a7ecb59f31fa20 wolf | 19: 0x7f37bc3ebebc - std::sys::backtrace::__rust_begin_short_backtrace::h7eb3c69899e21f7b wolf | 20: 0x7f37bc4003b2 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h99ab421c2966aafd wolf | 21: 0x7f37bc5a79df - <std[52919eca6bce4da3]::sys::thread::unix::Thread>::new::thread_start wolf | 22: 0x7f37cbae57f1 - <unknown> wolf | 23: 0x7f37cbb76944 - __clone ``` and am no longer able to connect after that until i restart wolf. attached are the debug logs for each connection [connection3.log](https://github.com/user-attachments/files/32347888/connection3.log) [connection2.log](https://github.com/user-attachments/files/32347887/connection2.log) [connection1.log](https://github.com/user-attachments/files/32347889/connection1.log) the error does not happen if i just use ctrl-alt-shift-q and then reconnect later
Sign in to join this conversation.
No milestone
No project
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#307
No description provided.