I’ve downloaded Xojo 2024R3 to my Intel Mac and whereas the IDE worked fine on some smaller projects, it is really unusable on our main project (>1200 classes).
On initial load the IDE is fine - I can load the project and navigate. As soon as I open a UI layout, it starts to slow down, the CPU usage goes up and stays up. After an initial debug compile, the IDE is completely unusable - 100%CPU usage and no UI response. This is repeatable every time. I’ve had no similar issues with Xojo 2024R1.1.
What you do not say:
your OS / OS version
Installed RAM
Your boot mass storage (HDD / SSD / Cloud)
Use (or not) of GIT (or similar),
Changes after the initial Debug session,
Number of concurent running applications
I didn’t post about my machine as there were no problems with any previous versions of Xojo, but here they are:
OS: Sonoma 14.5
16Gb RAM
44GB free disk
2.6 Ghz 6-Core i7
Using git (so plain text project)
A couple of small code changes after the first debug session
Outlook and Teams are the only applications running
The layout I’m working on has about 100 controls (difficult to count as there are several custom controls).
I’ll do some more experiments to see if I can pin down what the specific cause is.
Here’s the memory usage of Xojo 2024R3:-
Initial load (project chooser showing, no project loaded): 1.80Gb
Load big project (only “no selection” tab open): 3.23Gb
Run app in debug mode (click the Xojo “Run” button): 9.45Gb
Close app normally: 9.29Gb
Close project: 8.29Gb
Load project again: 9.15Gb
Run app in debug mode again: 15.25Gb
Close app normally: 15.10Gb
It’s about this time that the IDE becomes unusable.
Interestingly, I did the exact same steps in Xojo 2024R1.1 with virtually identical results, so the memory leak is in that version too.
Normally, I wouldn’t close the project and re-open, so maybe I don’t hit this precise sequence of events very often (I’ve had out of memory messages occasionally in the past).
Anyway, the good news is this isn’t specifically a Xojo 2024R3 problem - the bad news is that it’s a problem in the last few versions too.
I have found intel chips to be terrible for xojo dev on Mac with large projects. I have had xojo using 33gigs and had to reboot / restart xojo every few hours. This has been happening for many many years. Solution was dev on windows or upgrade to Apple silicon. Less memory and zero performance issues
You nearly got it … (size of free rooms on disk, Xojo used memory).
Add the Undo mechanism (and time: the more you use it the more memory is used) and your Virtual Memory in your HDD boot disk is on his knees… you see a drastic slow down in performances.
Free space on your boot volume (use a fast SSD) and give us the results.
Hmmm. The memory leaking is definitely worse in 2024R3 than in 2024R1.1. Just a couple of adjust/debug/adjust/debug cycles and the memory usage brings the IDE to its knees.
I think 44Gb free disk space is more than enough - I don’t think that’s the problem. There’s definitely a problem with 2024R3 which I wasn’t having with 2024R1.1. The memory leaks mean 2 cycles of change/debug is all that is possible. The debugger doesn’t seem to clean up between debug cycles.
Does this sound familiar to anyone else? Wasn’t there was a bug a few versions ago which would cause the IDE to do never-ending refreshes if certain controls (containers?) were present, or overlapping? Was it popup menus or maybe calendars?
I thought it was fixed, but maybe it’s back, or a new variation?