For anyone who is having similar issue clearing the userdirectory usually fixes the problem. You can do this via help-> user directory and either move or delete the contents of that folder.
Regards,
M.Y. Developers
For anyone who is having similar issue clearing the userdirectory usually fixes the problem. You can do this via help-> user directory and either move or delete the contents of that folder.
Regards,
M.Y. Developers
Great news! I am back in business thanks to the developer chatting with me today. For the issue editing not possible, I had to delete some directories and relaunch Glider. Now back to my app! A lot of bugs to crush before the Apple deadline!
Thanks again.
Mo
@Mo,
Thanks for the update! Has the high CPU utilization problem resolved?
Regards,
M.Y. Developers
Yes so far. I will keep post it if something change. THANK YOU so much for taking the and have a chat to resolve this issue.
Mo
Hello Mo,
You’re welcome! Sure, please let us know if you come across any issues.
Regards,
M.Y. Developers
I have LuaGlider2 which I just downloaded two days ago, and a macbook Air. I am also having extremely high CPU utilization and an almost completely unresponsive IDE.
Which directories do I need to delete?
Any other suggestions? I already only scan stubs.
Correction: I had it set to Scan Only Current File + requires. Now it’s set to Scan Only stubs. It does seem to be better.
How will that impact Glider’s functionality?
Hello Tntwickey,
Glider has a fairly complex code analysis suite. With that complexity comes lots of features such as occurrences finder, instant rename rename refactoring, goto declaration, and custom class based auto complete entries. Longer files on particular (more than a few thousand lines can slow things down especially if editing). Is this the case for you?
turning on stubs only mode will force glider to deep scan only the auto complete stubs created by us and will fallback to a much simpler plain text indexer system that is guarantee to run at O(n) time. This will still give acceptable results at least on par with other ides.
At any rate we would like to fix the problem. A stripped down sample project that demonstrates the problem will help us a lot. If that is not an option then uploading logs via help>upload logs will also help.
Regards,
M.Y. Developers
I’ve got the same problem, fan is cranking.
Glider 2.0 is using 207 under CPU reading in monitor, it’s using 50% of my capacity while idle in the background…EEEEEK!
I’ve got Stubs only set as tntwickey suggested. Without changing the scan, Glider is totally unusable, can’t scroll or even place the cursor without up to 5 sec. of lag.
Features are great, but if they can’t be utilized…well, basically just useless. Basically options are useless.
Another thing, I can’t get auto complete to stop adding the matching brackets or quotes…really frustrating.
edit:
my CPU usage climbed to 308, I had to terminate all background scanning located at the bottom of the window, which is a bummer as I share files with drobox between my PC and Mac Air.
My Glider 2.0 CPU usage dropped to 15 from over 300.
I can’t imagine I’m the only 2 users seeing this
btw, I’m using Mavericks.
edit 2:
I thought I turned off backround
scanning totally, but I must not have. I changed something at the
bottom of the window, but when I added an image to my project folder,
Glider updated it in the projects window, so it must still be scanning
for changes which is great.
So I’m not sure what I
changed at the bottom of the main window, but now my CPU is at 7,
running smooth and still scanning my projects folder. hmmmm
Nail
Hello Nail,
Is auto completion working properly?
Regards,
M.Y. Developers
Hey MY,
No, I can’t turn auto complete off for matching brackets/quotes/braces
Unfortunately, over time, the CPU climbed to over 325 and Glider became unresponsive again.
Hello Nail,
Please upload the logs via help-> upload logs. We will review it and do whatever is necessary to get this to work.
Regards,
M.Y. Developers
MY, sent the logs. Didn’t see how to label them, I’m still using the “trial”, haven’t looked again to see if I got an update email notice yet so not sure how you know they are from me.
If you need me to send them again, just let me know here.
Nail
Hello Nail,
Thank you for the logs. We see a bunch of exceptions that might be leading to the slowness. We will come up with a fix for you to try soon.
Regards,
M.Y. Developers
Good deal, thanks for the help. I hope the fixes are relatively painless, GL.
Nail
Hello Nail,
There is an update that should hopefully fix the issue. Please get it from help-> check for updates. The exceptions should go away and the performance issues should also hopefully resolve.
Regards,
M.Y. Developers
I got the update, Glider seems to be holding around 100 CPU now. I haven’t been much yet since on vacation. I’ll let you know more when I get back to it.
I still have the matching quotes/braces thing happening.
Nail
Hello Nail,
Hmm, it seems it is stuck in a loop somehow. Does the problem happen all the time or when opening a particular project? Please upload logs when you get a chance, in the meantime enjoy the vacation.
Regards,
M.Y. Developers
Hey MY,
After hoveering around 100 - 115 for most of the day, I decided to close Glider and open it again.
When it reloaded, CPU went to 200+ and holding steady.
I then closed the project I’m working on and played with a Test code project which is substantially smaller and was in the project window, the CPU stayed 200+.
I closed Glider again and reloaded it with only the Test project loaded. CPU was about 5.
I then reopened my current project and CPU spiked to +200 momentarily, but quickly dropped back to 5.
In the background it’s only using 2.3 CPU.
At some point, the CPU is going to ramp up again, probably stuck in a loop I would think, I’m just not sure when it happens.
Hope this helps,
Nail
Hello Nail,
Another thing, I can’t get auto complete to stop adding the matching brackets or quotes…really frustrating
Do you mean after you type open quote or open parenthesis it automatically closes it? If you have to take your hand off the homekey to press the right arrow then this can get very frustrating. Instead you should just close it as you normally would and the IDE should be smart enough to replace the one already there instead of creating a syntax error.
Thanks for the detailed information and the logs. Unfortunately the logs do not really give us any more information. If it is not too much trouble would it be possible to have a stripped down version of your project (without art assets, it need not even compile properly.) We will then test it ourselves and try to replicate the problem on our end so we can fix the issue.
This would be much appreciated and of course any code you give us will be promptly deleted unless you also want us to add it to our integration tests.
Please send to our email:
Regards,
M.Y. Developers
MY wrote:
Do you mean after you type open quote or open parenthesis it
automatically closes it? If you have to take your hand off the homekey
to press the right arrow then this can get very frustrating. Instead you
should just close it as you normally would and the IDE should be smart
enough to replace the one already there instead of creating a syntax
error.
Yes this is what I mean, a simple bothersome example would be when I want to print a variable value, since the IDE adds the closing quote, I have to go to the right arrow to jump the automatically added quote to enter the comma and variable.
print("print this == ", value)
I don’t want the IDE to add any quotes or parenthesis or anything to my typing.
I can’t stop it from adding the closing quote or parenthesis, even though disabled in “code completion”.
I haven’t coded anyting, but have done several build and runs with my project and have left Glider running in the background and haven’t seen the CPU climb since I last re-opened my project. I’ve also opened and re-loaded Glider several times this morning and haven’t seen the CPU spike and hold, it’s always coming back down to <5 now like it probably should.
I’ll let you know if I see the CPU climb again, but for now everything is running properly.
Nail