enricobuehler 5e27f65f2e fix(host/capture): mmap the buffer fd ourselves — xdpw MemFd over-reads MAP_BUFFERS ...

The CPU de-pad path trusted PipeWire's MAP_BUFFERS slice (`d.data()`, length =
`data.maxsize`). xdg-desktop-portal-wlr hands MemFd ScreenCast buffers whose
maxsize exceeds the bytes PipeWire actually maps into our process, so reading to
maxsize ran off the end of the mapping and SIGSEGV'd the capture thread —
crashing every CPU-path capture on Sway/wlroots (and thus any non-NVIDIA host,
which has no CUDA zero-copy importer and always falls back to this path).

mmap the fd ourselves, sized to its real length (fstat), for any fd-backed
buffer (MemFd SHM or DmaBuf); fall back to `d.data()` then drop. The existing
`needed > avail` guard now drops cleanly instead of over-reading. This also
subsumes the original "MAP_BUFFERS didn't map a Vulkan dmabuf" fallback.

Verified: fixes real Sway-desktop portal capture -> VAAPI HEVC on a Radeon 780M
(correct image + colours); the NVIDIA zero-copy path (returns before this code)
and the NVIDIA/KWin CPU path (self-mmap, fd_len == maxsize) both still work.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-19 21:48:49 +00:00

..

protocols

rename: lumen → punktfunk, everywhere

2026-06-10 13:11:59 +00:00

src

fix(host/capture): mmap the buffer fd ourselves — xdpw MemFd over-reads MAP_BUFFERS

2026-06-19 21:48:49 +00:00

build.rs

fix(dist): kill the version-shadow + add build provenance (P0)

2026-06-15 10:30:21 +00:00

Cargo.toml

refactor(host/zerocopy): dlopen libcuda instead of a link-time #[link]

2026-06-19 15:44:57 +00:00