I noticed an annoying problem with 2014r2.
After some time Im working on it it starts becoming incredibly slow. This is true for every task, from editing code to compiling.
I dont really understand what causes this, but it seems happening when working with more than one open project and/or two workspaces.
Needless to say, the same doesnt happen with 2014r1.1
(OS X 10.9.4)
[quote=110402:@Massimo Valle]I noticed an annoying problem with 2014r2.
After some time Im working on it it starts becoming incredibly slow. This is true for every task, from editing code to compiling.
I dont really understand what causes this, but it seems happening when working with more than one open project and/or two workspaces.
Needless to say, the same doesnt happen with 2014r1.1
(OS X 10.9.4)
Someone else noticed this behavior?[/quote]
Yes, I have the noticed the same slowness after using IDE in long sessions. But I had this issue with 2014r1.1 too. I’m coding in my mac air 8GB of RAM vs 16 of my desktop computers and the laptop slows downs more often.
I am using also Cocoa MBS plugins, if that could help to fix this issue.
I have noticed that R2 didn’t seem to address very many of the IDE issues… cursor still goes where it wants, so you end up typing in the code area instead of adding a parameter list… etc.
IDE still has the issue when every time you do a build it eats RAM. On a smallish project my Xojo RAM usage is over 1.8GB and continues to creep up. If you have multiple instances of Xojo open then it gets even worse. I am running on Windows 8.1 with 16GB Ram and an 8GB virtual RAM (on an SSD drive) and after about 5 hours I have to exit Xojo r2 and restart as it just becomes like treacle.
Pardon my ignorance. What steps should we do to send you feedback information? This bug is driving me nuts when I have to code +12 hours a day. Will do all I can to help you reproduce and fix this bug, but I am unsure how to proceed.
If you go into the task manager and right click a process, there is a create dump file option. But I wouldn’t know if that was of any use to anyone there or not.
The sample looks absolutely normal and like what the IDE should be doing. You should start the sample in Activity Monitor and then switch back immediately to the IDE to make it exhibit the slow behavior.