[BUG] Critical video error

[yourjelly]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Every 15 minutes or during use the video stream dies and flashes between the following error and reconnecting for several seconds before resolving again for a period of time

Expected Behavior

No response

Steps To Reproduce

I don't know what specifically triggers it but it seems to happen often during component placement.

Environment

- OS: Unraid
- How docker service was installed: VIA unraid app gallery

CPU architecture

x86-64

Docker creation

/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='kicad' --net='swagnet' --pids-limit 2048 -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Monolith" -e HOST_CONTAINERNAME="kicad" -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='XXX' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/kicad-logo.png' -p '3151:3001/tcp' -v '/mnt/user/appdata/kicad':'/config':'rw' 'lscr.io/linuxserver/kicad'

Container logs

Res: 1358x746 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 61.00 EncStripes/s: 61.00
INFO:data_websocket:Received STOP_VIDEO
INFO:data_websocket:Stopping X11 x264-striped capture...
Capture loop stopped. X resources released.
INFO:data_websocket:Frame-based backpressure logic task cancelled.
INFO:data_websocket:Frame-based backpressure logic task finished.
INFO:data_websocket:Backpressure task was stopped. Calling _reset_frame_ids_and_notify.
INFO:data_websocket:Resetting frame IDs.
INFO:data_websocket:Broadcasting PIPELINE_RESETTING to 1 client(s).
INFO:data_websocket:Received START_VIDEO for encoder: x264enc
INFO:data_websocket:Starting x264enc: 1358x746 @ 60.0fps, CRF: 25, FullFrame: True
INFO:data_websocket:New frame backpressure task started (current encoder: 'x264enc').
INFO:data_websocket:x264enc capture started successfully.
INFO:data_websocket:Frame-based backpressure logic task started.
INFO:data_websocket:Client settings received, proceeding with backpressure loop.
X Shared Memory Extension available.
XShm setup complete for 1358x746.
CPU cores available: 8
INFO:webrtc_input:Set clipboard content, length: 25
Res: 1358x746 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 6.00 EncStripes/s: 6.00
INFO:data_websocket:Received STOP_VIDEO
INFO:data_websocket:Stopping X11 x264-striped capture...
Capture loop stopped. X resources released.
INFO:data_websocket:Frame-based backpressure logic task cancelled.
INFO:data_websocket:Frame-based backpressure logic task finished.
INFO:data_websocket:Backpressure task was stopped. Calling _reset_frame_ids_and_notify.
INFO:data_websocket:Resetting frame IDs.
INFO:data_websocket:Broadcasting PIPELINE_RESETTING to 1 client(s).
INFO:data_websocket:Received START_VIDEO for encoder: x264enc
INFO:data_websocket:Starting x264enc: 1358x746 @ 60.0fps, CRF: 25, FullFrame: True
INFO:data_websocket:New frame backpressure task started (current encoder: 'x264enc').
INFO:data_websocket:x264enc capture started successfully.
INFO:data_websocket:Frame-based backpressure logic task started.
INFO:data_websocket:Client settings received, proceeding with backpressure loop.
X Shared Memory Extension available.
XShm setup complete for 1358x746.
CPU cores available: 8
INFO:webrtc_input:Set clipboard content, length: 25
Res: 1358x746 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 37.00 EncStripes/s: 37.00
Res: 1358x746 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 60.00 EncStripes/s: 60.00
INFO:data_websocket:Received STOP_VIDEO
INFO:data_websocket:Stopping X11 x264-striped capture...
Capture loop stopped. X resources released.
INFO:data_websocket:Frame-based backpressure logic task cancelled.
INFO:data_websocket:Frame-based backpressure logic task finished.
INFO:data_websocket:Backpressure task was stopped. Calling _reset_frame_ids_and_notify.
INFO:data_websocket:Resetting frame IDs.
INFO:data_websocket:Broadcasting PIPELINE_RESETTING to 1 client(s).
INFO:data_websocket:Received START_VIDEO for encoder: x264enc
INFO:data_websocket:Starting x264enc: 1358x746 @ 60.0fps, CRF: 25, FullFrame: True
INFO:data_websocket:New frame backpressure task started (current encoder: 'x264enc').
INFO:data_websocket:x264enc capture started successfully.
INFO:data_websocket:Frame-based backpressure logic task started.
INFO:data_websocket:Client settings received, proceeding with backpressure loop.
X Shared Memory Extension available.
XShm setup complete for 1358x746.
CPU cores available: 8
INFO:webrtc_input:Set clipboard content, length: 25

[thelamer]

That is a client error, what is the client you are using ? Browser and pc specs, nvidia decoders are the most finicky, but only really ever goes fatal on striped or 4:4:4 color mode.

[yourjelly]

Chrome, i9-12950HX, 32 GB ram, and Nvidia RTX A4500
I'm surprised to hear it's a client issue, as I've not noticed it with any other Silkies container applications

[thelamer]

As a test you can try chrome with the --disable-gpu cli param:

I am not saying this is a permanent solution but it is worth a try to see if it is more stable for you.

The only other thing I can think of is it possible you have this open on another device or tab somewhere? The server is single client outside of shared modes and other people connecting can mess with it.

You can also try clearing all your cache including application storage in the developer console on the client.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[thelamer]

Another thing of note an nvidia video card has a decoder cap, it is 4-8 depending on drivers and card, if you use it for other decoding or other apps you can hit this cap. And unlike other apps that can fallback to cpu encoding the webcodecs api is relatively new and it just works or it does not depending on the underlying hardware we don't get clear errors from the api.

[yourjelly]

Gotcha, I was having the same issues with another computer at home (also Nvidia), it seems like it might be related to having heavy gpu usage cad software open. I haven't used it with my chromebook yet to see if it crops up there or the --disable-gpu option to see if that clears it up, as it was less of an issue with the cad software closed.

[thelamer]

I'm not telling you this as stating this is what is happening, these are just my theories.

The disable GPU test to see if you still get resets is the best test, if you don't you know the hardware decoder is getting disabled for some reason, if you still get the resets it is something else.

[yourjelly]

Using the CPU encoding toggle seems to have resolved it.