obsproject
[macOS] Window Capture pauses when window is minimized
Operating System Info
Other
Other OS
macOS 26
OBS Studio Version
32.0.0
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/g7b3bvmdrbAXzO67
OBS Studio Crash Log URL
No response
Expected Behavior
It should keep recording the application which I minimize.
Current Behavior
When I minimize the application that is being recoded using front stage on macOS 26, it just records the minimized window other than the whole application. It's probably the question of the new OS26, because it just happened after I update the OS26.
Steps to Reproduce
...
Anything else we should know?
No response
It has happened to me a few times this week. I also have to restart the capture frequently for my sources . dont know if its only me having this issue
I have observed this behaviour a lot with MacOS over the years since Monterey and up to Tahoe and I am certain that this is not an OBS problem. I believe this is an optimisation feature of the MacOS compositor (WindowServer) as when if no pixels are visible in a window on the desktop because there are other windows on top of it or the window is minimised (as you state), then there is no need to render it to preserve precious GPU and CPU cycles. MacOS is simply not choosing to render your app because no pixels are visible. All you have to do is force the Window to always show, either by keeping it visible on another monitor (Virtual spaces don't count unfortunately), or you can also set borderless full-screen window mode (not exclusive full-screen mode) and that should be enough as there is an invisible 1px line below the menu bar which cannot have normal windows with a border put over it, this and the fact that most window corners are rounded help a borderless full-screen window stay visible to the WindowServer even if the borderless window gets pushed to the back of the Window order. Try this for yourself and see how you get on. I firmly do not believe there is any other way to make this work having monitoring this issue myself for quite a long time. I have sent feedback to Apple about this but that always seems like copying a file to /dev/null. Good luck!
