I just downloaded 2019 R2.1 which was released yesterday and was testing an application I had been working on in 2019 R2. (Originally had been working fine with 2018 R3 and I was moving to a current version of Xojo, but ran into some problems. So it seemed timely that 2019 R2.1 was just released.)
I was testing modal windows I use for a date picker, which 2019 R2 ‘broke’ by always opening the modal in the centre of the screen. 2019 R2.1 has a fix to open the modal window where the bounds are set. The modal window does open in the correct location, but it is now crashing my application. Both in debug and a built 32-bit application. (I have not tried 64-bit because when I did build 64-bit it destroyed my app preference file and I have not gone back to figure out why.)
I can reproduce the problem by opening and closing a modal window 3 or 4 times and then get the crash.
Application Specific Information:
*** CFRelease() called with NULL ***
I’m not sure if this is something in my code causing this, I don’t think so since this is working fine with 2018 R3, but thought I would ask and see if there is anything I can do. (Without having to move all my changes back into 2018 R3.) Anyone else see this problem?
As this part of the r2.1 code was touched, maybe a bug. You need to create a sample and explain how to reproduce the crash, and make a feedback app post about it. Maybe this is the first r2.1 bug, justifying an r2.2, found.
10.13 was the last 32bit compatible MacOS. 10.14 has quirks, in 10.15 it is dead. Xojo 32 bit apps should have some kind of init check and stop running with a message of incompatibility for any 10.14+
Xojo customer building 32 bits applications have to implement that.
Thank you for adding this sentence, you are 100 % right.
A released application, nowadays, have to be 64 bits, but if it is 32 bits this have to be done: we never know what a user can do (volunteer or by mistake) and come back to us ranting !
Nope. Because it must the first thing to do. It must be a compiler job. Or more complex calls at user space or even initing the framework, could crash the app before it doing its job.
10.13 and 14 run 32 bit apps
10.15 wont even load them so there is no way for anyone, compiler or app developer, to put in any kind of warning since the OS itself WILL NOT load your 32 bit app at all - so anything put in CANNOT show, ever, In a 32 bit app