[Bug 273224] After process finishes shared memory resourced aren't released: shmget() failed: No space left on device
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273224] After the process finishes shared memory resourced aren't released: shmget() failed: No space left on device"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273224] After the process finishes shared memory resourced aren't released: shmget() failed: No space left on device"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273224] After the process finishes shared memory resourced aren't released: shmget() failed: No space left on device"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 273224] After the process finishes shared memory resourced aren't released: shmget() failed: No space left on device"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 19 Aug 2023 06:31:20 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273224
Bug ID: 273224
Summary: After process finishes shared memory resourced aren't
released: shmget() failed: No space left on device
Product: Base System
Version: 13.2-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs@FreeBSD.org
Reporter: yuri@freebsd.org
I use x11vnc which uses shmget(2).
The system was up for 2+ months and x11vnc was launched maybe hundreds of
times.
Today it failed all of a sudden:
> shmget() failed: No space left on device
x11vnc is launched as a new process every time the user connects to the local
display.
This means that when x11vnc finishes it doesn't release resources that
shmget(2) allocates.
Ultimately shmget(2) becomes a time bomb which blows up eventually and x11vnc
(and probably all other software that uses shmget(2)) becomes unusable until
the system is rebooted.
FreeBSD 13.2
---References---
* Someone had the same problem on Linux 12 years ago:
https://blog.dhampir.no/content/fixing-shmget-failed-no-space-left-on-device
--
You are receiving this mail because:
You are the assignee for the bug.