I only manage to start Xojo when no plugins are used.
At no time, even after trying 10 times or more, do I succeed in starting Xojo when MBS Plugins are used.
I have already reduced the number of plugins to the ones I need (see screenshot).
Maw I cannot upgrade to Ventura on my main system which I find super annoying. Just because Xojo doesn’t work.
I use Xcode daily. It loads a lot more (and really a lot more) dylib compared to Xojo. But Xcode always starts up from the first time.
My conclusion is that Xojo does not load the plugins correctly (anymore). I also get the impression that Xojo Inc shrugs its shoulders about this and doesn’t consider it a major problem. This is very regrettable.
And at some point, because of this, I will just have to leave Xojo behind me.
Why is it that only Xojo has a problem with this? I mean, they’re a lot of app that load dylibs (Xcode more than 100, Final Cut Pro when plugins are installed it can be over 100 easily,…). I have yet to see another app fail to do this.
Maybe we can conclude Xojo doesn’t do this correctly?
Do you know another product that has the same problem with dylibs besides Xojo?
If there are no other products affected by their dylib bug I don’t think Apple will dedicate the time to fix the problem (their product is not crashing).
I hope Xojo can find a workaround to Apple’s bug before too long.
Keep in mind that Xojo has its own plugins, both public (database plugins) and private (necessary for the IDE to work). If the IDE works fine without any third party plugins, this isn’t necessarily a Xojo problem. I’m not saying that it’s not, but the chances are relatively low.
The fact that it works just fine in macOS 12 and not in macOS 13 means that Apple changed and probably broke something. It could also be that they finally made a change to something that’s been deprecated for a while. It would not surprise me for instance if Apple put an arbitrary limit of 256 or 512 dylibs for some reason and when you reach that threshold, things get unstable.
I’ve also managed to create a relatively consistent repro using Emacs. Still crashes on macOS 13.2.1 for me. Thankfully I only load in the low 100s of dylibs so it only takes me a restart or two to get it open. Then, because it’s Emacs, I often have it open for days or weeks.
Assume that you’ve gotten your answer as to the likelihood of this issue being resolved. If you really want to use Apple’s latest and greatest, you’re going to have to reduce your dependencies. Right now, you’re dependent on 3 different vendors, cutting it back to just 2 (or even 1) would solve this situation.
I am a single human being also. The trick is not to re-invent the wheel, but to use the one that’s already there in the macOS.
One of the things that really got to me in the end is Xojo providing 60~80% of what I need, but to get that last 40~20%, I have to rip out and replace their classes.
