Lua Glider issues on Mac

Glider (IDE)
#1

I recently purchased Lua Glider and loved it compared to some of the other IDE’s I’ve used. But lately it’s become quite unusable and I’m going to get a refund if this issue can’t be resolved.

I have a small project (about 12 lua files each about 100-300 lines long) and I am able to open up my project and work on it for about 10-20 minutes before the spinning beachball comes up for 20-30 seconds at a time after every single keypress or mouseclick. I have to force quit to get out.

I’ve lost work because of this, which is the biggest no-no for a development tool.

This issue hasn’t happened with any other Lua editor I’ve tried.

Does anyone else have this issue or any resolution? I’ve uninstalled the program, including the application support data and reinstalled, but still get the same problem.

I’m on a 2009 iMac with Mountain Lion with not much else running except a browser.

Also, if there are any suggestions for an alternatives with good debugging support, I’d love to hear them.

#2

Are your project files on an external/network drive?

#3

@Zrm310,

We are sorry you are having so many problems. There is an autosave feature that saves all modified files to your user directory every x seconds (default 5 minutes.) Please see the following screenshot:

http://view.xscreenshot.com/f9c24e70ee29bcc036cb770e9ba4726d

We also ask you upload your logs so we can diagnose the problem via help-> upload logs. 

One more thing you should try that will fix most if not all instability issues is to turn off scanning. Please see the following:

http://view.xscreenshot.com/50be67f9bd9f37ee77c49371c6e6571e . 

Please let us know if that fixes the issue, then at least we will know what the culprit was.

Regards,

M.Y. Developers

#4

This same problem is so bad on my mac that I cannot do anything anymore. I cannot even change the setting to turn off background processing because background processing has taken over. I am as frustrated as @Starter. 

#5

@staytooned,

Please go to help-> user directory and delete the contents of it. If you cannot access the menu then see the screenshot:

http://view.xscreenshot.com/e21a086926e8bca538b7a40583a9e891

This will revert Glider to a pristine state. You will then be able to get to the options menu.

Regards,

M.Y. Developers

#6

@ M.Y.developers

Thanks for the response and suggestions. I uploaded the logs. There are only a few since I recently reinstalled the app. The messages.log.1 seems to show a lot of indexing happening towards the end of the file when the slowdown happened again. 

Re: turn off scanning. On the Mac version, there is no “Scan only stubs” so I set it to “Scan only current file + requires” for now to see if that will make a difference.

#7

Hello zrm,

Thanks for the logs. You need to update Glider via help-> check for updates. We aren’t sure which version you are running but lots of stability fixes have happened after we introduced the “scan only stubs” feature.

Regards,

M.Y. Developers

#8

@ M.Y.developers

Thanks. I had the version downloaded from your website a few days ago which didn’t have that pref option. I updated and now it has it and I have set it to “scan only stubs”. So far half a day without any issues, so that may have solved it. Thanks for all your help!

BTW, what feature am I losing by turning off scanning. Was that indexing for faster searches or something else?

#9

@zrm310,

Glad that is working for you.

BTW, what feature am I losing by turning off scanning. Was that indexing for faster searches or something else?

In order to have some advanced features such as:

  • Code navigation (ie go to declaration/implementation)
  • Usage search
  • Globals highlighting
  • Class aware/parameterized code completion
  • Unused variable detection

Glider needs to scan and analyze your lua code. Since lua is a dynamic language the only way to figure out the input/outputs of a function are is to scan through it and “execute” it. In the end this allows us to infer stuff about your code to give you the features listed above.

If you do not use these features then you will probably be happier just turning off the scanning. You will still get Corona autocomplete and a plain text index based autocomplete of the current file. You should turn on scanning when you wish to experiment with the above features. 

Regards,

M.Y. Developers

#10

@zrm310,

Just making sure it is working better for you. Have you encountered any issues since then?

Regards,

M.Y. Developers

#11

@ M.Y.developers,

Thanks for checking. It’s a lot better and usable for hours every day. It’s a great tool and become my IDE of choice. 

I only regret not be able to use the advanced features you mention as my project grows larger, since whenever I turn on scanning it grinds the program to a halt and makes it unusable within 20 minutes.

Any idea why the scanning is so slow for even a small project? Is it possibly incorrectly also scanning non lua files in the project directory?

#12

Hello Zrm310,

We are constantly improving the storage engine so you may want to try this:

http://view.xscreenshot.com/c5891817cb86392a0bf2164ecb0f864b

This should fix the slowness problem if it stems from memory usage. 

Regards,

M.Y. Developers

#13

Hi M.Y.developers,

Thanks for the suggestion; I’ll give it a try. Not sure if that’s a new option, as “Use RAM storage” was already checked on mine. But I’ll switch the scanner detail back to “Scan main.lua…” and see if the same slowdown happens or not.

When everything works, I love your program. I’m new to Lua and Corona so I’m still amassing tools, but this is the only IDE I’ve found that approaches other environments I’m used to.

#14

Hello Zrm310,

Sorry about the ambiguity, we meant to uncheck the RAM storage option so that it can swap stuff to the disk when needed. However if you have it checked and it is working for you that is an even better sign. We have got quite a few more features planned so if you miss something from your other environments then let us know.

Regards,

M.Y. Developers

#15

Are your project files on an external/network drive?

#16

@Zrm310,

We are sorry you are having so many problems. There is an autosave feature that saves all modified files to your user directory every x seconds (default 5 minutes.) Please see the following screenshot:

http://view.xscreenshot.com/f9c24e70ee29bcc036cb770e9ba4726d

We also ask you upload your logs so we can diagnose the problem via help-> upload logs. 

One more thing you should try that will fix most if not all instability issues is to turn off scanning. Please see the following:

http://view.xscreenshot.com/50be67f9bd9f37ee77c49371c6e6571e . 

Please let us know if that fixes the issue, then at least we will know what the culprit was.

Regards,

M.Y. Developers

#17

This same problem is so bad on my mac that I cannot do anything anymore. I cannot even change the setting to turn off background processing because background processing has taken over. I am as frustrated as @Starter. 

#18

@staytooned,

Please go to help-> user directory and delete the contents of it. If you cannot access the menu then see the screenshot:

http://view.xscreenshot.com/e21a086926e8bca538b7a40583a9e891

This will revert Glider to a pristine state. You will then be able to get to the options menu.

Regards,

M.Y. Developers

#19

@ M.Y.developers

Thanks for the response and suggestions. I uploaded the logs. There are only a few since I recently reinstalled the app. The messages.log.1 seems to show a lot of indexing happening towards the end of the file when the slowdown happened again. 

Re: turn off scanning. On the Mac version, there is no “Scan only stubs” so I set it to “Scan only current file + requires” for now to see if that will make a difference.

#20

Hello zrm,

Thanks for the logs. You need to update Glider via help-> check for updates. We aren’t sure which version you are running but lots of stability fixes have happened after we introduced the “scan only stubs” feature.

Regards,

M.Y. Developers