obs-studio icon indicating copy to clipboard operation
obs-studio copied to clipboard

[MacOS] UI not working properly

Open tonygoldcrest opened this issue 2 years ago • 11 comments

Operating System Info

macOS 14

Other OS

No response

OBS Studio Version

30.0.0

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/uaJ2YojeqgU28mLl

OBS Studio Crash Log URL

No response

Expected Behavior

  • UI works normally
  • The app exits normally

Current Behavior

  • Most of the UI Elements, such as pop-up menus, settings windows, etc, not working. DEMO: https://share.cleanshot.com/75XXRk4b
  • Application not responding when trying to close, hanging forever

Steps to Reproduce

  1. Open OBS
  2. Try to click UI elements
  3. Observe it not working

Anything else we should know?

At first, the only issue I had was the app hanging forever when trying to close it. A couple of days ago, however, all UI elements stopped working. This can be sometimes overcome by opening the "Settings" menu, which triggers other windows to show (behavior seen in the demo video I attached), but it does not work for popup menus, which means I cannot configure filters, etc. I've previously been using MacOS Ventura when I started seeing this issue and thought that maybe updating to Sonoma would fix it, but unfortunately, this didn't help. Maybe this is relevant, but I have a dual external monitor setup, however, the issue is reproducible even without plugging them in, with the native monitor.

I thought that the app not closing properly and the UI elements not working are related issues, because the first couple of times when I opened the app after updating to Sonoma, the issue was not there and the app was closing normally.

Hope that can be fixed, as I'm unable to modify any settings at the moment.

tonygoldcrest avatar Dec 06 '23 02:12 tonygoldcrest

The video looks like the Properties and Filters windows have spawned either under the application or possibly on a different display. When you open the Settings window, it seems as if the child windows have been pulled back to OBS' current display.

RytoEX avatar Dec 07 '23 23:12 RytoEX

Yeah, that's what I thought, although the windows are not appearing anywhere on the other screen too. "Show all windows" doesn't show anything except for what is already visible.

Moreover, whereas hidden windows I can deal with by clicking "Settings", the bigger problem is that the popup menus are not showing, such as when you right-click on a scene item/the plus button in the filters menu - these are not shown when Settings is clicked, presumably because they are hiding on outside click, which happens when I click other buttons.

Also, as I mentioned in the description, the issue is reproducible when I disconnect the monitors and run just the native MacBook display.

tonygoldcrest avatar Dec 08 '23 00:12 tonygoldcrest

One more thing that I observed, although I'm not 100% sure that's the case: When I open OBS, it opens on my secondary monitor, no matter where I start the application. I think the windows/popups were opening correctly when OBS opened on my main monitor, which was the case in the beginning, when I just installed the app, and at some point, it permanently switched to opening on a secondary monitor for some reason. Given that I always start after a crash, maybe it is always restoring the previous state of being on the secondary monitor or something.

tonygoldcrest avatar Dec 08 '23 00:12 tonygoldcrest

the bigger problem is that the popup menus are not showing, such as when you right-click on a scene item/the plus button in the filters menu

This sounds like Qt-related behavior where it does not correctly determine what display the popup menus should spawn on (or we are spawning them at incorrect coordinates).

Maybe this is relevant, but I have a dual external monitor setup, however, the issue is reproducible even without plugging them in, with the native monitor.

Also, as I mentioned in the description, the issue is reproducible when I disconnect the monitors and run just the native MacBook display.

When running the external monitors, is the MacBook display active at all? Or is the MacBook display turned off (or the MacBook is closed).

Given that I always start after a crash, maybe it is always restoring the previous state of being on the secondary monitor or something.

This could be the case, yes. Window geometry and position are saved, and may not be saved correctly if OBS is crashing on shutdown.

RytoEX avatar Dec 08 '23 02:12 RytoEX

When running the external monitors, is the MacBook display active at all? Or is the MacBook display turned off (or the MacBook is closed).

The lid is closed. I've just tested it with the lid open, and it does not spawn windows either. However, when the lid is open and two external monitors are connected, OBS opens on the MacBook display, not the secondary monitor.

tonygoldcrest avatar Dec 08 '23 13:12 tonygoldcrest

This could be the case, yes. Window geometry and position are saved, and may not be saved correctly if OBS is crashing on shutdown.

Maybe the state that it had saved upon the crashless exit I had in the past had some geometry/positions that are not available anymore, but I cannot break out of this state because I cannot exit the app properly, hence the windows/popups are spawning incorrectly?

tonygoldcrest avatar Dec 08 '23 13:12 tonygoldcrest

In my case it more and more happens that OBS just wont open anymore. OBS processes are very busy, menu bar item is there but does not respond , no windows opening, restart makes no difference

matthiasg avatar Jan 03 '24 13:01 matthiasg

I have the same problem Mac M1, Ventura 13.1 OBS 30.1.2

If I open OBS normally and close it I get a window that says "OBS Studio Quit Unexpectedly. Click Reopen to open the application again. Click Report to see more detailed information and send a report to Apple" The next time I open OBS it has a window that says "OBS did not shut down properly during your last session. Would you like to start in Safe Mode" If i run it in Safe Mode the windows still don't show up, but when I close it again it doesn't crash. Then finally if I open it again it doesn't suggest safe mode, and the UI works as it should

So for now I have to open OBS 3 times every time I want to use it. This problem started before version 30 of OBS and I still can't find out why. It seemed to happen randomly but maybe one of my plugins like Streamdeck updated automatically and messed with something?

UnknownTurtle2 avatar May 21 '24 16:05 UnknownTurtle2

I have the same problem Mac M1, Ventura 13.1 OBS 30.1.2

If I open OBS normally and close it I get a window that says "OBS Studio Quit Unexpectedly. Click Reopen to open the application again. Click Report to see more detailed information and send a report to Apple" The next time I open OBS it has a window that says "OBS did not shut down properly during your last session. Would you like to start in Safe Mode" If i run it in Safe Mode the windows still don't show up, but when I close it again it doesn't crash. Then finally if I open it again it doesn't suggest safe mode, and the UI works as it should

So for now I have to open OBS 3 times every time I want to use it. This problem started before version 30 of OBS and I still can't find out why. It seemed to happen randomly but maybe one of my plugins like Streamdeck updated automatically and messed with something?

Please ask in our support channels about your crash. This issue is mostly about Qt-related screen/window geometry issues, not crashes.

RytoEX avatar May 22 '24 00:05 RytoEX

Please ask in our support channels about your crash. This issue is mostly about Qt-related screen/window geometry issues, not crashes.

hi, I think I explained it badly, but I have the same UI issue as this post where the UI pop-ups don't show up. Even the part that opening the settings menu can get other windows to show. I think the "crash" after closing OBS is what's mentioned in by the original post as "Application not responding when trying to close, hanging forever"

UnknownTurtle2 avatar May 22 '24 03:05 UnknownTurtle2

I'm also experiencing this issue on my Mac and can confirm in my case that it's directly related to having extended displays. When OBS would open, if it wouldn't freeze, it wouldn't response to being opened through spotlight using command+tab. I would have to press control up and find the window and click on it to make it active. I also could not open any filter or properties pop-ups: pressing "show all active windows" would show only the main window and nothing else.

When I unplug my extended display, it works immediately without any issues.

brianz41 avatar Jul 04 '24 22:07 brianz41

same issue here. I can't fix my webcam settings now. and OBS keeps crashing when I close it. Opening OBS without an external monitor doesn't fix this

Crashed Thread:        0  CrBrowserMain  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes:       0x0000000000000001, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [78080]

VM Region Info: 0 is not in any region.  Bytes before following region: 4363616256
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      104178000-104588000    [ 4160K] r-x/r-x SM=COW  /Applications/OBS.app/Contents/MacOS/OBS

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0   Chromium Embedded Framework   	       0x310595ac0 0x30b0a4000 + 89070272
1   Chromium Embedded Framework   	       0x310595888 0x30b0a4000 + 89069704
2   CoreFoundation                	       0x19b4ef9c4 ___forwarding___ + 212
3   CoreFoundation                	       0x19b4ef830 _CF_forwarding_prep_0 + 96
4   obs-browser                   	       0x12e16979c 0x12e138000 + 202652
5   obs-browser                   	       0x12e169630 0x12e138000 + 202288
6   obs-browser                   	       0x12e1696e0 0x12e138000 + 202464
7   OBS                           	       0x1043a9db8 0x104178000 + 2301368
8   OBS                           	       0x1042d4cf4 0x104178000 + 1428724
9   OBS                           	       0x1042d5ae0 0x104178000 + 1432288
10  QtCore                        	       0x106e443f4 QObject::event(QEvent*) + 680
11  QtWidgets                     	       0x107346018 QWidget::event(QEvent*) + 3216
12  QtWidgets                     	       0x10745e070 QMainWindow::event(QEvent*) + 716
13  QtWidgets                     	       0x1072fcb68 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272
14  QtWidgets                     	       0x1072fe4f8 QApplication::notify(QObject*, QEvent*) + 3280
15  QtCore                        	       0x106e00af0 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 292
16  QtCore                        	       0x106e019e0 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 500

gianpaj avatar Jan 28 '25 11:01 gianpaj