LBN: [Update: Public RC Available]
I had Ventura 13.3 installed earlier this week.
Yesterday I had 3 crashes in a row, while opening the IDE.
After the 4th attempt It finally worked.
So, I guess the problem is still lurking around to present itself at random. 
Just saying that does not help. You must collect all postmortem information you can and submit them in an issue report for analysis. Maybe you have some “very” incompatible plugin needing update for example.
FWIW, I typically don’t use plugins and the IDE is crashing on me twice a day, even in 13.3.
1 Like
Using Ventura 13.3.1 on an iMac m1, 2023 Release 1 crashes sometimes exactly when I click on a tab at the top of the IDE window to view my code while my application.debug is running in the IDE. I’m using no plugins. For me it hasn’t crashed under any other procedure or situation.
Is the window you click on a Window by any chance. There is an issue with a window with many controls causing crashes in 2023r1, could it be that?
Repeatable hard crash when clicking on a window with a lot of controls.
1 Like
Crash on launch or while using?
The dylib thing is only a problem when starting Xojo.
With all MBS Plugins installed on macOS 13.2.1 it still crashes a lot on startup.
Someone has claimed that macOS 13.3 fixes the issue, nothing before that. As far as I am aware there is no 13.3.1 version. I’m on the beta program and the next beta is macOS 13.4.
It is fixed in 13.3
and for what’s worth, the current latest version is macOS 13.3.1 (released a week ago).
Ah, mine went from 13.3 beta to 13.4 without anything in between. 
Yep, probably that is related with the bug pointed by @Ian_Kennedy and that is fixed already for a coming 2023r1.1 release.
MacOS 13.4.1 Apple M1 Max - Xojo Version 2023 1.1
I have - rarely - crashes, mostly without a report during ‘cut’ operations. Maybe keeping the IDE open for a long time? Why isn’t there a configurable timer to automate ‘Save’?
Hi @Karl_Grob
Very probably that is related with a problem other than the original from this thread 
For getting a better picture of your issue you may prefer to open a new thread and it would be very helpful if you open a new issue for it providing as many details you can the next time it happens. That would help us a lot.
Thank you so much! 
I cannot open a new issue because there is no report and nobody remembers exactly what was the exact configuration every time he uses ‘Cut’ within the coding process, when this happens once in several days. Thus it is not reproducible → “case closed”.
A timer for “Save” in the Preferences would be a good feature anyway. (Nobody is forced to use it).
There are video recorders which continuously keep the last minute. Have you checked the console and the crash reports? A crash without a crash report is rare.
There is an Austrian Author Nestroy. I quote: “Die Wirklichkeit war schon immer der beste Beweis für die Möglichkeit”. (The reality has always been the best Proof of the possibility.) “Save” is triggered anyway through the coding activity - I just cannot imagine the reason for not using this old fashioned feature.
BTW: If it was only the last minute, there would be no problem. The problem is that I forget to Save if I am concentrated in my work and this can go for an hour. This is my problem, not the one of Xojo, but a triggered “Save” would be helpful. That’s all what I suggest.
As a workaround you could add a BuildScript which applies to Debug Mode and add a
DoCommand("SaveFile")
within it.
1 Like
I use it as a small script under “windows”. Everytime I run the code for debugging it will save the code automatically.