[BUG] Mouse and keyboard input either stops completely or has huge delay

[terrin2k]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I am running the latest release build (v2.3.1-ls106) as of this report.

After some (random?) amount of time after the container is started, mouse and keyboard input either stops working entirely, or suffers from a huge (~10 second) lag.

The only resolution I've found so far is to restart the container.

Thanks for your assistance!

~ D

Expected Behavior

Mouse and keyboard input are passed to the UI.

Steps To Reproduce

• Container is running on an Open Media Vault server on my local network
• I use firefox browser to connect to the container's UI
• After some random number of minutes interacting with OrcaSlicer, the UI stop registering keyboard or mouse, or in some cases, the input is delayed by ~10 seconds.

Environment

- OS:Open Media Vault
- How docker service was installed: distro's package manager (debian apt)

CPU architecture

x86-64

Docker creation

---
services:
  orcaslicer:
    #user: "nobody:nogroup"
    image: lscr.io/linuxserver/orcaslicer:latest
    container_name: orcaslicer
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - /path/to/config:/config
      - "/srv/dev-disk-by-uuid-f058d43e-6e7c-43c2-9547-c9fa4988dc00/work/:/container/work:rw"
#      - type: bind
#        source: /srv/dev-disk-by-uuid-f058d43e-6e7c-43c2-9547-c9fa4988dc00/work/
#        target: /container/work
#        read_only: false
        
    ports:
      - 3000:3000
      - 3001:3001
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/dri/card0:/dev/dri/card0
    restart: unless-stopped

Container logs

[orcaslicer_docker_log.txt](https://github.com/user-attachments/files/23242465/orcaslicer_docker_log.txt)

[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]

Its the DRI3 implementation on iGPUs I have no idea what it is but some kind of memory threshold is hit and xvfb is permanently stuck like this the stream is actually all making it to you the lag and messed up session is xvfb choking on drm calls to the iGPU.
This is way more prevelant on low end intel iGPUs like n series and particularly if the igpu is not hard configured with a block of memory.

But in your case it might just be missing the shm size directive.

[terrin2k]

Thanks for the reply!

I tried specifying shm_size in my compose file and tried a number of different sizes (1g, 2g, 3g) and it didn't seem to help.

The little headless PC I'm using to serve my containers does indeed have a low-end Intel iGPU.

Do you have any other suggestions?

Thanks!

~ D