Xojo 2022R3.1 crashes galore

Targets macOS
101

:rofl:

1 Like
102

Craig Federighi Admits Apple’s Beta Programs Don’t Provide the Interaction and Influence Many Users Desire

An astonishing insight:

Apple’s senior vice president of software engineering, Craig Federighi, has admitted that the company’s beta testing program, which offers developers and public beta testers access to beta versions of iOS, iPadOS, watchOS, tvOS, and macOS, isn’t effective in giving users the amount of influence and interaction they desire.

1 Like
103

I heard this one today.

“Apple cares about keeping your data private, in that they’ve been collecting it, privately”.

2 Likes
104

For those of you impacted with the Ventura + MBS plugins issue, I tried this and it is working here every single run of the Xojo IDE. (It can be seen as a workaround until Apple fixes the dlopen thing).

The setup:

  • MacBook Pro - M1 Pro - 16 GB - Ventura 13.1 Beta 3.
  • The plugins folder inside the Xojo folder is an alias pointing to the real plugins folder stored in an external USB stick. (That one containing the by default plugins + all the MBS plugins suite).

It is working here every time I Run the Xojo IDE
 without crashes.

3 Likes
105

Wow. What a workaround, what format is the USB stick? Earlier Christophe mentioned FAT32, which IIRC does not support Apple’s ACls or xattrs


Have you tried from a DMG file?

106

The USB stick is way slower than a normal hard disk. That could mean a race condition.

107

No AFAIK from our side of the code involved in the process


108

Some Engineer at Apple may love Timers


109


or blocks inside dlopen stuff


2 Likes
110

So this may be related to new security features that may be disabled outside APFS, and instead of firing an error for unsecured conditions, it just ignores, and load it anyway? Formatting an NTFS partition could work too? Instead of using a pen-drive that removed will break things?

1 Like
111

Does not sound like blocking to me if it only crashes some of the time. Block would block always. Sounds more like some sort of memory clobbering. And given the logs then its probably something to do with the path, how that is handled.

1 Like
112

Try substituting a disk image for the USB stick and see what happens. Make sure it is the same format.

1 Like
113

That was one of my concerns also, especially as the path for dlopen is char and not string or CFString.

114


it crashes.

115

Let’s keep in mind that everything works (AKA: same code) in Monterrey. :slight_smile:

1 Like
116

Has anyone submitted a DTS/TSI? For another related ventura crashing bug, my TSI was responded to within 24 hours (they didn’t fix it or have a workaround, but they seem aware of the issue).

117

What does this mean, heck it didn’t crash in dlopen on Monterey either.

In the past I had a problem with char path encodings on a newer version of the macOS, it was something I was doing wrong, that was accepted in older versions of the macOS, but they changed it.

1 Like
118

Then it’s not you that was doing wrong; it’s the change that shouldn’t have taken place :wink:

1 Like
119

The changes should or must occur. People must to know and adapt. In the past a file named today as “Reçu Rapport GĂ©nĂ©rique.XLS” should be written as “recu_rapport_generique.xls” due to lack of internationalization. Once introduced, mixing older and newer machines, you could end with one working ok, and in another the filename would corrupt as “Re?u Rapport G?n?rique.XLS”. Changes for the best sometimes comes with initial pain, but it does not mean you should avoid it.

120

Just: why?

I’d say the problem is the lack of internationalisation in the first place.