macOS: Closing OBS via window close button removes Twitch docks and causes layout/auth state loss on next launch

[schwarzkopfb]

Operating System Info

macOS 26

Other OS

No response

OBS Studio Version

32.1.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/vAbZuifxBJIN50Bp

OBS Studio Crash Log URL

No response

Expected Behavior

OBS should preserve Twitch browser docks, dock layout, and Twitch authentication state regardless of how the application is closed.

Closing OBS via:

• OBS → Quit OBS
• Cmd+Q
• the macOS red window close button

should all result in the same persisted state after relaunch.

Current Behavior

When OBS is closed using the macOS red window close button, Twitch browser docks disappear immediately before the application fully closes.

After reopening OBS:

• Twitch docks are gone
• dock layout is not preserved

The issue does NOT occur when quitting OBS via:

• OBS → Quit OBS
• Cmd+Q

Using those methods preserves the Twitch docks and layout correctly.

Steps to Reproduce

1. Connect a Twitch account inside OBS
2. Enable Twitch docks (e.g. Chat and Stream Information)
3. Arrange and dock the panels normally
4. Close OBS using the macOS red window close button
5. Reopen OBS

Result:

• Twitch docks disappear or reset
• layout persistence breaks

Control test:

• If OBS is closed via OBS → Quit OBS or Cmd+Q instead, the issue does not occur.

Anything else we should know?

• macOS 26.5 (Apple Silicone)
• Twitch docks are browser-based (CEF)
• The issue originally appeared after installing/removing the Aitum Vertical plugin, although the plugin has since been fully removed
• Clearing OBS browser cache helped stabilize the application state, but the issue still reproduces specifically when using the macOS window close button
• Browser hardware acceleration does not appear to be the cause
• The issue seems related specifically to shutdown order/state persistence during window-close termination

[Fenrirthviti]

Probably a duplicate of #13440 which is fixed by #13445

Please test artifacts on that PR if this fixes your issue.