Error message running non-stop, simulator not responding

[David_Y]

Hi,

The following error message keeps running non-stop whenever the Terminal is opened.

“[some datetime value here]…Corona Simulator [926:507] Got error in FileWatch LastTimeModification”

I have to use Control +C to log out or right-click at the Simulator icon to force quite the Simulator since it is not responding. 

I have tried the following: 

1. Edited the main.lua file to include only a simple ‘Hello World’ print statement to ensure the main.lua file does not contain error;

2. There was one time I waited until the Simulator showed up and then specified the ‘relaunch simulator whenever the file is modified’ to Never;

3. dropped the Corona icon to trash and emptied it and reinstalled Corona

I have the Corona Starter and use BBEdit for code writing.

I am new to Corona and can see its great potential. Any help will be greatly appreciated.

[bjsorrentino]

Hi David,

Can you tell me which version of Corona you downloaded? Is it the most recent public build? Which OS version are you using?

Thanks,

Brent Sorrentino

[David_Y]

Hi Brent,

It is CoronaSDK-2013.12.02.dmg, installed on a Mac Mini running OS X 10.9 Mavericks.

Some additional info:

Prior to this error, I have had fun learning it without any problem. I wonder if it have something to do with BBEdit to which I recently switched. I used TextMate before.

When I right click at the non-responding Simulator, I can see 5 main.lua file icon showing in it. I couldn’t open any of them, though.

I also tried right click at a main.lua file and choose Open with Corona Simulator. The file will eventually open in the correct iPhone simulator and showing the correct content. However, the screen will become frozen and not responding. The terminal will have the above mentioned error message looping non-stop, with some brief pauses in between.

Thanks,

David

[AlanPlantPot]

Is it happening in every project, or just a particular one?

I’ve found that occasionally if there is an error in my code, the simulator gets trapped in an error loop even if I restart it and it shouldn’t have reached the scene with the error yet. Only when I fix the error, kill the simulator and then restart does it solve this problem.

With regards to the 5 main.lua files when you right click, that’s normal. I think it shows the last X number of projects that were opened in Corona (although it’s totally unhelpful to just see “main.lua” without knowing which project each one belongs to).

[David_Y]

It happens on every project. Whenever I open the terminal the error message will start looping. It seems like Corona is stuck at the last error. This happened when I started writing a main.lua file to read in a small SQLite data file that has only two rows. So the crash is not because of the data size.

[bjsorrentino]

Hi David,

Please try the latest public build, 2076, released yesterday, and see if this issue still occurs.

https://developer.coronalabs.com/downloads/corona-sdk

Thanks,

Brent

[David_Y]

Downloaded the latest build, got the same error. Kept trying and got it to work eventually. In case someone else may run into this in the future, here are the steps that worked for me:

1. Open the Corona folder, right click at a main.lua file from one of the SampleCode folders, choose Open with Corona Simulator. Make sure it works, then quit the Simulator. This seems to clear the “memory” of the last main.lua file that generated the error.

2. Now click at the Simulator icon to open it, there will be a list of Recent Projects. Whatever you do, Don’t click at the last project that produced the error. Instead, click at a project that worked before, or choose Open and navigate to the folder that contains the main.lua file that you want to open, and open the main.lua file.

Thanks to Brent and AlanPlantPot for staying with me and help through this.

[David_Y]

Turns out there is an even simpler workaround. At least on my machine, this error only occurs if the main.lua and associated files are in the Home folder. Moving the main.lua file and associated files into a subfolder under Home or under another location solves the problem. I have to avoid using the Home folder, but it is not a big deal. Not sure if this is related to Corona, or Mavericks, or just  my machine.

[bjsorrentino]

Hi David,

Can you tell me which version of Corona you downloaded? Is it the most recent public build? Which OS version are you using?

Thanks,

Brent Sorrentino

[David_Y]

Hi Brent,

It is CoronaSDK-2013.12.02.dmg, installed on a Mac Mini running OS X 10.9 Mavericks.

Some additional info:

Prior to this error, I have had fun learning it without any problem. I wonder if it have something to do with BBEdit to which I recently switched. I used TextMate before.

When I right click at the non-responding Simulator, I can see 5 main.lua file icon showing in it. I couldn’t open any of them, though.

I also tried right click at a main.lua file and choose Open with Corona Simulator. The file will eventually open in the correct iPhone simulator and showing the correct content. However, the screen will become frozen and not responding. The terminal will have the above mentioned error message looping non-stop, with some brief pauses in between.

Thanks,

David

[AlanPlantPot]

Is it happening in every project, or just a particular one?

I’ve found that occasionally if there is an error in my code, the simulator gets trapped in an error loop even if I restart it and it shouldn’t have reached the scene with the error yet. Only when I fix the error, kill the simulator and then restart does it solve this problem.

With regards to the 5 main.lua files when you right click, that’s normal. I think it shows the last X number of projects that were opened in Corona (although it’s totally unhelpful to just see “main.lua” without knowing which project each one belongs to).

[David_Y]

It happens on every project. Whenever I open the terminal the error message will start looping. It seems like Corona is stuck at the last error. This happened when I started writing a main.lua file to read in a small SQLite data file that has only two rows. So the crash is not because of the data size.

[bjsorrentino]

Hi David,

Please try the latest public build, 2076, released yesterday, and see if this issue still occurs.

https://developer.coronalabs.com/downloads/corona-sdk

Thanks,

Brent

[David_Y]

Downloaded the latest build, got the same error. Kept trying and got it to work eventually. In case someone else may run into this in the future, here are the steps that worked for me:

1. Open the Corona folder, right click at a main.lua file from one of the SampleCode folders, choose Open with Corona Simulator. Make sure it works, then quit the Simulator. This seems to clear the “memory” of the last main.lua file that generated the error.

2. Now click at the Simulator icon to open it, there will be a list of Recent Projects. Whatever you do, Don’t click at the last project that produced the error. Instead, click at a project that worked before, or choose Open and navigate to the folder that contains the main.lua file that you want to open, and open the main.lua file.

Thanks to Brent and AlanPlantPot for staying with me and help through this.

[David_Y]

Turns out there is an even simpler workaround. At least on my machine, this error only occurs if the main.lua and associated files are in the Home folder. Moving the main.lua file and associated files into a subfolder under Home or under another location solves the problem. I have to avoid using the Home folder, but it is not a big deal. Not sure if this is related to Corona, or Mavericks, or just  my machine.