Are you using Glider 2.0? I’ve been running it on my Macbook air with 4gb of ram and haven’t seen any performance degradation at all so far.
Yes, I am using Glider 2.0. The problem only starts to happen after using it for a long time… the CPU starts to be overloaded while the memory stays around 800mb. I have 16gb on my MAC, so it shouldn’t be any memory problem, but if glider limit itself to use only ~800mb and thens starts to do IO on disk, maybe this causing the cpu overload… But being honesty, I don’t think that is the problem, because all Glider starts to freeze… not only when editing the code… even trying to click on the top menu (File, Edit,…) is slow…
I put some screenshots of my Activity Monitor here: http://forums.coronalabs.com/topic/41123-when-it-will-be-released-a-new-version-of-glider/#entry224066
Can you define a long time? I’ve run it for 8 hours on my iMac and about 4 hours at a time on my macbook air with no issues.
I haven’t looked into the memory usage, but I have the same 16gb of ram on my iMac also, along with an SSD.
The issue sounds strange… I hope I can help you get to the bottom of it. 
Thanks for trying it out. Please let us know if that indeed fixes the issue or only delays the eventual decline.
The problem only starts to happen after using it for a long time… the CPU starts to be overloaded while the memory stays around 800mb
Glider is running in a JVM so it will not use any more memory than what is alloted (in this case 800mb.) When it reaches this threshold the garbage collector frantically tries to reclaim memory resulting in a huge CPU spike. Eventually 99% of the CPU time is spent in GC and this triggers an out of memory condition and the heap is dumped to disk, which is probably the disk activity you are seeing. We are still trying to figure out why leaks occur for some but not for others. Perhaps it may be due to the size of the files or the number of projects simultaneously open?
@Euphoria,
Thanks for your valuable input.
Regards,
M.Y. Developers
MY, I’ll jump on the thread to confirm this issue still exists on my MacBook Air also. It always seems to freeze at the wrong time.
Sometimes even after a force close and reload the CPU will stay over 200.
Nail
Just providing more info: My Glider it is only with 5 projects in the Projects Tab and I was with only 3 files opened.
I spoke too soon.
I also got this slowdown happen to me last night.
I think the key is having more than one project in your projects tab. Previously I only had one project in there, then last night I added another project and worked on that and boom, got the slowdown.
Hope this helps in narrowing this down MYDevelopers.
Pre 2.0 I had dozens of Projects in the Project Tab, but when I installed to 2.0 decided to only have my active project - unfortunately still prone to slowdowns. Admittedly it happens far less frequently then pre 2.0 - but still occasionally happens, usually when I’m prone to leaving Glider running for days upon days.
Hello All,
There is an update that should alleviate the problem.
Regards,
M.Y. Developers
What does the other memory settings affect?
-Xms64m
-J-XX:MaxPermSize=256m
My team are working on a large project with many larger files etc. Some config/script files can be above 2000 lines. And sometimes lua glider feels a bit slow even tho i have a 2013 macbook pro with 8gb ram.
Is there anything else you can do to enhance the perfromance of luaglider?
Hello Samuel,
What does the other memory settings affect?
-Xms64m
-J-XX:MaxPermSize=256m
-Xms64m just sets the minimum memory allotment. This number usually is not relevant. The one you want to tweak is the Xmx512m.
-J-XX:MaxPermSize is the “permanent generation” memory area. This is java talk for things that are not garbage collected like classes, string literals, etc. Earlier version of Glider had issues with permgen but now you can probably get away with decreasing this value.
Regards,
M.Y. Developers