Wont capture full size or other windows, captures itself

[Sorcecoder]

Description

One day it stoped working (after upgrading to new versions and even downgrading does not give me a working app. Screenshots are not taken properly... (blue take screenshot is visible on the screenshot)

Reproduction

I updated to the latest version. Putting chrome in full size on macos makes it unavalable to capcut. Also full screen capture does not work at all.

Additional Context

• Cap version: 0.4.83
• Operating system, version: MacOS 15.7.3 (Sequoia)
• Device (optional): Apple M4 Pro 14-inch, Nov 2024

2026-04-14T13:05:20.892280Z INFO take_screenshot{target=Window { id: WindowId(WindowIdImpl(14843)) }}: cap_recording::screenshot: Fast capture result: image dimensions = 2386x1648
2026-04-14T13:05:21.012936Z INFO cap_desktop_lib::frame_ws: WebSocket server listening on port 64082
2026-04-14T13:05:21.031337Z INFO cap_desktop_lib::frame_ws: Socket connection established
2026-04-14T13:05:21.036501Z INFO cap_rendering::yuv_converter: Creating shared YUV converter pipelines (shader compilation)
2026-04-14T13:05:21.037023Z INFO cap_rendering::yuv_converter: Shared YUV converter pipelines created successfully
2026-04-14T13:05:21.037030Z INFO cap_rendering::yuv_converter: Initializing YUV converter textures (using shared pipelines) gpu_max_texture_size=8192
2026-04-14T13:05:21.037777Z INFO cap_rendering::yuv_converter: Creating shared YUV converter pipelines (shader compilation)
2026-04-14T13:05:21.038029Z INFO cap_rendering::yuv_converter: Shared YUV converter pipelines created successfully
2026-04-14T13:05:21.038857Z INFO cap_rendering::yuv_converter: Initializing YUV converter textures (using shared pipelines) gpu_max_texture_size=8192
2026-04-14T13:05:21.038957Z INFO cap_rendering::yuv_converter: Creating shared YUV converter pipelines (shader compilation)
2026-04-14T13:05:21.039261Z INFO cap_rendering::yuv_converter: Shared YUV converter pipelines created successfully
2026-04-14T13:05:21.040111Z INFO cap_rendering::yuv_converter: Initializing YUV converter textures (using shared pipelines) gpu_max_texture_size=8192
2026-04-14T13:05:21.217426Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=10000 elapsed_ms=1
2026-04-14T13:05:21.219069Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=20000 elapsed_ms=3
2026-04-14T13:05:21.220589Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=30000 elapsed_ms=5
2026-04-14T13:05:21.222127Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=40000 elapsed_ms=6
2026-04-14T13:05:21.223649Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=50000 elapsed_ms=8
2026-04-14T13:05:21.225285Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=60000 elapsed_ms=9
2026-04-14T13:05:21.226909Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=70000 elapsed_ms=11
2026-04-14T13:05:21.228436Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=80000 elapsed_ms=12
2026-04-14T13:05:21.229999Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=90000 elapsed_ms=14
2026-04-14T13:05:21.231534Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=100000 elapsed_ms=15
2026-04-14T13:05:21.233216Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=110000 elapsed_ms=17
2026-04-14T13:05:21.234992Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=120000 elapsed_ms=19
2026-04-14T13:05:21.236910Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=130000 elapsed_ms=21
2026-04-14T13:05:21.238664Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=140000 elapsed_ms=23
2026-04-14T13:05:21.240304Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=150000 elapsed_ms=24
2026-04-14T13:05:21.241972Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=160000 elapsed_ms=26
2026-04-14T13:05:21.243614Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=170000 elapsed_ms=28
2026-04-14T13:05:21.245250Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=180000 elapsed_ms=29
2026-04-14T13:05:21.262895Z INFO cap_desktop_lib::frame_ws: WS frame stats fps=0 mb_per_sec="2.9" avg_kb="5760.0" dims="2386x1648" format="NV12"
2026-04-14T13:16:56.317228Z INFO cap_desktop_lib::frame_ws: WS frame stats fps=1 mb_per_sec="5.9" avg_kb="5760.0" dims="2386x1648" format="NV12"
2026-04-14T13:16:58.759753Z INFO cap_desktop_lib::frame_ws: WS frame stats fps=2 mb_per_sec="17.8" avg_kb="6935.6" dims="2576x1838" format="NV12"
2026-04-14T13:17:01.105795Z INFO cap_desktop_lib::frame_ws: WS frame stats fps=1 mb_per_sec="10.7" avg_kb="6935.6" dims="2576x1838" format="NV12"
2026-04-14T13:17:04.602847Z INFO cap_desktop_lib::frame_ws: WS frame stats fps=0 mb_per_sec="3.6" avg_kb="6935.6" dims="2576x1838" format="NV12"
2026-04-14T13:17:06.868385Z INFO cap_desktop_lib::frame_ws: WS frame stats fps=16 mb_per_sec="117.2" avg_kb="6935.6" dims="2576x1838" format="NV12"
2026-04-14T13:17:09.285031Z INFO cap_desktop_lib::frame_ws: WS frame stats fps=5 mb_per_sec="39.1" avg_kb="6935.6" dims="2576x1838" format="NV12"
2026-04-14T13:17:13.208029Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=10000 elapsed_ms=2
2026-04-14T13:17:13.210534Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=20000 elapsed_ms=5
2026-04-14T13:17:13.213163Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=30000 elapsed_ms=8
2026-04-14T13:17:13.214033Z INFO cap_desktop_lib::frame_ws: WS frame stats fps=0 mb_per_sec="3.6" avg_kb="6935.6" dims="2576x1838" format="NV12"
2026-04-14T13:17:13.216585Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=40000 elapsed_ms=11
2026-04-14T13:17:13.218995Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=50000 elapsed_ms=13
2026-04-14T13:17:13.221292Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=60000 elapsed_ms=16
2026-04-14T13:17:13.223505Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=70000 elapsed_ms=18
2026-04-14T13:17:13.225784Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=80000 elapsed_ms=20
2026-04-14T13:17:13.228078Z WARN cap_rendering::frame_pipeline: GPU buffer mapping taking longer than expected frame_number=0 poll_count=90000 elapsed_ms=23

[linear]

CAP-682

[tembo]

This issue appears related to a few known problems with ScreenCaptureKit on recent macOS versions. A couple of observations that might help with debugging:

Related Issues:

• GetShareableContent/DisplayMissing error when recording a window on macOS 26.3.1 #1654 reports DisplayMissing errors when recording windows on macOS 26 - the display lookup from the selected window returns a display ID that doesn't match any display in SCShareableContent.displays(). A suggested workaround there was using desktopIndependentWindow filter.
• [DevEx] Local dev builds unable to test screen recording on macOS Sequoia — TCC/ScreenCaptureKit completely broken for unsigned binaries #1722 documents TCC/ScreenCaptureKit issues on Sequoia where CGPreflightScreenCaptureAccess() returns false for unsigned/ad-hoc binaries regardless of permissions.

Relevant Code Paths:

• The screenshot functionality uses CGWindowListCreateImage for window capture in crates/recording/src/screenshot.rs:270-278. For window captures, it uses kCGWindowListOptionOnScreenOnlyBelowWindow (option 0x00000008) with kCGWindowImageBoundsIgnoreFraming.
• The issue mentioning "captures itself" and "blue take screenshot is visible" suggests the Cap window is not being properly excluded when capturing. The exclusion logic is in crates/recording/src/sources/screen_capture/macos.rs:204-227 using as_content_filter_excluding_windows.
• For fullscreen Chrome specifically, this could be related to macOS treating fullscreen windows differently in ScreenCaptureKit. The window capture path at crates/recording/src/screenshot.rs:847-859 uses sc::ContentFilter::with_desktop_independent_window which should work for fullscreen windows.

Diagnostic Questions:

1. Does this happen with all windows or specifically Chrome?
2. Does selecting "Display" capture instead of "Window" capture work correctly?
3. Are you using any external displays alongside the built-in display?

The GPU buffer mapping warnings in your logs (GPU buffer mapping taking longer than expected) suggest there may be some rendering pipeline delays, but those shouldn't directly cause the capture-itself behavior.