< Back to IRCAM Forum

Can't load the workspace in OM 7.1

Karim,

I now manage to be able to launch OM over time BUT only if there is no other app open (other then the finder) and even more, with no finder window open (window manager issue ?)

Y

Very Bizarre. I have the same config as you have, and many apps openned: Terminal Firefox, etc.

Whta you mean by “with no finder window open” ?
MAybe your problem comes from the desktop settings of your OS preferences ?

OM won’t launch if anything else is open, including even a window from the Finder.
Hence the suspect “WindowServer process”.
There is not much I can do in mac os with desktop settings. I always have default settings.

Y

Does this happens even when you create a new workspace?

Yes, any workspace. even a new empty one.
The workspace is not the issue, I’m sure of that.
I just logged all system events of the different settings (om won’t launch / om launch) to see the difference and I’ll get back to you.
Best

Ok, i found an article about the WindowProcess on Mac:

Apparently, there are many reasons that this happens. Do you have:

  1. Many monitors?
  2. a new mac Intel or an older model?
  3. Is your desktop cluttered with icons (folders and stuff?)

just the mackbook
16-inch, 2019 (that makes it old right ?)
nothing on the desktop.

Not necesssary so. I have almost the same thing:

But it might be an issue with RAM.
My patch is working here:


I say check out your RAM.

Here are some system log infos (in case that might help)…
launch-OK.txt (6.0 KB)
launch NOT-OK.txt (5.4 KB)

Will do a ram text.
Y

RAM ok.

Will try to get better log infos using “sudo log stream” when I will get the right --predicate to filter om…
Y

According to the logs you’ve sent, it might be that when you log out or exit your session OM was still running and somethig called tristan.FSMonitor also:

18:13:16 :x: 0x10200 /Users/yanmaresz/Library/Saved Application State/com.tristan.FSMonitor.savedState/window_1.data
18:13:16 :x: 0x11200 /Users/yanmaresz/Library/Saved Application State/com.tristan.FSMonitor.savedState/windows.plist
18:13:16 :x: 0x11200 /Users/yanmaresz/Library/Saved Application State/com.tristan.FSMonitor.savedState/data.data
18:13:16 :new: 0x19500 /Users/yanmaresz/Library/Saved Application State/com.tristan.FSMonitor.savedState/window_1.data
18:13:16 :new: 0x10100 /Users/yanmaresz/Library/Saved Application State/com.tristan.FSMonitor.savedState/data.data
18:13:16 :new: 0x10500 /Users/yanmaresz/Library/Saved Application State/com.tristan.FSMonitor.savedState/windows.plis

What is this tristan thing?

Yes, I was using FSMonitor to log events…

But here are much better logs directly from the terminal.

results for :
sudo log stream --predicate ‘process == “OM 7.2”’
and
sudo log stream --debug --predicate ‘process == “OM 7.2”’

Archive.zip (114.7 KB)

Hope that helps…
Best

Y

the line :

OM 7.2: (AppKit) [com.apple.AppKit:Window] order window front conditionally: 4df related: 0
does not happen when OM does not launch properly.

so when OM launches properly we have :
OM 7.2: (AppKit) [com.apple.AppKit:Window] order window front conditionally: 4df related: 0
OM 7.2: (CoreFoundation) Loading Preferences From User CFPrefsD
OM 7.2: (CoreFoundation) Loading Preferences From User CFPrefsD
OM 7.2: (libsystem_info.dylib) Membership API: translate identifier
OM 7.2: (CoreFoundation) Loading Preferences From User CFPrefsD
OM 7.2: (CoreFoundation) Loading Preferences From System CFPrefsD
OM 7.2: (RunningBoardServices) didChangeInheritances
OM 7.2: (AppKit) trackMouse send action on mouseUp
OM 7.2: (AppKit) sendActionFrom:
OM 7.2: (AppKit) sendAction:
OM 7.2: (AppKit) [com.apple.AppKit:Window] order window: 4df op: 0 relative: 0 related: 0
OM 7.2: (RunningBoardServices) didChangeInheritances

versus :
OM 7.2: (CoreFoundation) Loading Preferences From User CFPrefsD
OM 7.2: (CoreFoundation) Loading Preferences From User CFPrefsD
OM 7.2: (libsystem_info.dylib) Membership API: translate identifier
OM 7.2: (CoreFoundation) Loading Preferences From User CFPrefsD
OM 7.2: (CoreFoundation) Loading Preferences From System CFPrefsD
OM 7.2: (RunningBoardServices) didChangeInheritances
OM 7.2: (AppKit) trackMouse send action on mouseUp
OM 7.2: (AppKit) sendActionFrom:
OM 7.2: (AppKit) sendAction:
OM 7.2: (AppKit) [com.apple.AppKit:Window] order window: 508 op: 0 relative: 0 related: 0
OM 7.2: (RunningBoardServices) didChangeInheritances
OM 7.2: (RunningBoardServices) didChangeInheritances

How much Ram you have?

16GB

these are the debug versions of the logs where the lines diverge beetwen “go and no go” versions.

(around line 2994)
OM 7.2: (CoreFoundation) [com.apple.defaults:User Defaults] found no value for key NSPersistentUIShowQuietSafeQuitStatus in CFPrefsSearchListSource<0x600002726f80> (Domain: fr.ircam.repmus.openmusic, Container: (null))
OM 7.2: (LaunchServices) [com.apple.launchservices:cas] Setting process information for [ kLSCurrentApp ASN, 0x0,0x2] .
OM 7.2: (LaunchServices) [com.apple.launchservices:cas] Setting process information for [ kLSCurrentApp ASN, 0x0,0x2] .
OM 7.2: (CoreFoundation) [com.apple.defaults:User Defaults] found no value for key NSPerformAutomaticTerminationImmediately in CFPrefsSearchListSource<0x600002726f80> (Domain: fr.ircam.repmus.openmusic, Container: (null))
OM 7.2: (LaunchServices) [com.apple.launchservices:default] LSExceptions shared instance invalidated for timeout.
OM 7.2: (LaunchServices) [com.apple.launchservices:default] LSExceptions [0x600000764c90] unloaded

Did you try to:

  1. trash OM preferences from ~/Library/Preferences
  2. reinstall OM 7.2
  3. put again the venturafix.lisp patch in the init folder of the newly installed OM .app

Launch again?

same thing.
sorry…
I’ll keep launching om with nothing else active and open.

Y

Dear Yan,

I am sorry for your situation. I tried to reproduce it on my machine in vain. I suspect this is something to do either with your setup, or due to lack of RAM. Just a guess.
Do you have something such as a antivirus running, or such?

Best
K

nope. nothing running.
But it’s ok Karim, I’ll manage.

Best
Yan

Dear Yan,

Can you try:

  1. install OM 7.2 anew from here:
    Release OM 7.2 · openmusic-project/openmusic · GitHub
  2. put this patch in the init folder inside OM 7.2 .app
    venturafix2.lisp (292 Bytes)

Just to try to sort things out.

Best
K