Corona Simulator crash on Runtime Errors

Solar2D General Questions/Discussion
#1

Hello Corona users!

I’ve got an annoying problem today with my Corona simulator.

I run v.2014.2511 of Corona SDK on Windows 7.

Yesterday everything was working fine, but today I run my project via Corona Simulator and everytime I hit a Runtime Error, Corona shuts down, keeping me from reading the terminal to solve the error.

I tried to reboot my PC and to reinstall Corona but the problem is still there.

What is strange is that I can manage to see the error in the terminal via screencapping very quickly before the program shuts down, and no matter what type of error (i tried with different intentional errors) it keeps closing!

Hopefully some of you know of a way to prevent Corona doing so!

Thank you in advance, I’m quite frustrated right now! Please HELP

#2

Hi @q-tro,

Can you provide any sense of what this error is, according to the screen capture you get? Can you upload that image here?

Thanks,

Brent

#3

Here is the latest one! (had to edit it a little bit for privacy reasons  :slight_smile: )
 
  vba7c.png
 
 
The triggering error is that I use a String as a number, which is a pretty easy error to solve, what I don’t want is Corona Simulator to shut down!

By the way… it reallly doesn’t matter what type of error it is: I always get the shutdown even in case of a simple syntax error. In fact, every Runtime Error cause the Simulator to shut down!

Also I really do not understand that nil at the end…
Hope you know of a solution! :wink:

#4

Sorry for the double post, but really, isn’t there anyone who can solve this problem??

I can’t even find anything on the web either… I’m preeeeeety much frustrated!  :wacko:

#5

Hi @q-tro,

Does the Simulator crash if you try to run one of our basic sample projects like “Hello World”? Please try this. It’s located in your local CoronaSDK application directory:

CoronaSDK > SampleCode > GettingStarted > HelloWorld

Brent

#6

Thank You @Brent Sorrentino, running the sample project and adding an intentional runtime error revealed that the simulator didn’t crash! So it was something about my project!!

Investigating really deep in the code I found out an error handling function that intentionally had this line, which generate the behaviour that I mistook for a bug!!

os.exit()

No one in my team told me that! 

Hope that this helps people figuring out the risks of teamwork and bad communication…  :unsure:

Lesson learned… the hard way!

#7

FYI:

The os.exit() API should never be called.   On iOS as iOS apps are not supposed to exit, so there is no reason to call it.  For Android and Windows 8 Phone, there is the native.requestExit() API call to properly exit those apps.

Rob

#8

Hi @q-tro,

Can you provide any sense of what this error is, according to the screen capture you get? Can you upload that image here?

Thanks,

Brent

#9

Here is the latest one! (had to edit it a little bit for privacy reasons  :slight_smile: )
 
  vba7c.png
 
 
The triggering error is that I use a String as a number, which is a pretty easy error to solve, what I don’t want is Corona Simulator to shut down!

By the way… it reallly doesn’t matter what type of error it is: I always get the shutdown even in case of a simple syntax error. In fact, every Runtime Error cause the Simulator to shut down!

Also I really do not understand that nil at the end…
Hope you know of a solution! :wink:

#10

Sorry for the double post, but really, isn’t there anyone who can solve this problem??

I can’t even find anything on the web either… I’m preeeeeety much frustrated!  :wacko:

#11

Hi @q-tro,

Does the Simulator crash if you try to run one of our basic sample projects like “Hello World”? Please try this. It’s located in your local CoronaSDK application directory:

CoronaSDK > SampleCode > GettingStarted > HelloWorld

Brent

#12

Thank You @Brent Sorrentino, running the sample project and adding an intentional runtime error revealed that the simulator didn’t crash! So it was something about my project!!

Investigating really deep in the code I found out an error handling function that intentionally had this line, which generate the behaviour that I mistook for a bug!!

os.exit()

No one in my team told me that! 

Hope that this helps people figuring out the risks of teamwork and bad communication…  :unsure:

Lesson learned… the hard way!

#13

FYI:

The os.exit() API should never be called.   On iOS as iOS apps are not supposed to exit, so there is no reason to call it.  For Android and Windows 8 Phone, there is the native.requestExit() API call to properly exit those apps.

Rob