Is anyone else getting simulator crashes/errors 50 times a day on Windows?

Solar2D Daily Builds and Public Releases
#1

I have previously mentioned this before but I am still getting several crashes every project reload. It crashes from either of two ways. One is the audio stops working, I get an audio already initialized message in the console and half the graphics dont load or appear and audio doesnt start. Calling anything with audio.* says that same error in the console. I then have to restart Corona. The second error and which crashes the simulator is after several project reloads, the project gets longer and longer to respond and then stops responding, crashes, or sometimes freezes PC and crashes my AMD graphics driver and eventually Windows recovers.

I have had a fresh install of Windows

I have sent a message to support at…corona and had no response

It is getting a real pain with both these problems.

It only seems to work on almost finished projects.

I cant seem to recreate  when I want. It just sometimes happens after 4 -10 project reloads.

I have only had these problems since the auto reload was implemented (audio bug) a few months ago but I learned to ignore it

and the graphics problem since the graphics 2 update.

It looks like project reloads are not purging something. I am not sure .

Someone there must have an idea or send me a corona release with crash report function ?

Using Vista, radeon AT HD2400.

#2

I’ve had issues similar to this. When my projects are reloaded very rapidly (15-20 seconds between reloads), after about the 10th reload in succession, random graphics in the project will show as black rectangles instead of the actual graphic. It doesn’t break my graphics driver or anything, but I do need to shut down and restart Corona. 

I haven’t felt this was so dire I needed to file a bug report, but I wanted to let you know you’re not crazy, and this wasn’t just happening to you. I’m sure it has to do with the new release of the Corona Simulator; I haven’t encountered this in device testing.

Did you file a bug report? If not, I’d suggest you do so. That’s the best way for Corona to take a look at your issue.

http://developer.coronalabs.com/content/bug-submission

#3

Heres a windows log for the graphics crash if that helps

Faulting application Corona Simulator.exe, version 13.0.2090.0, time stamp 0x529409c2, faulting module atioglxx.dll, version 6.14.10.11672, time stamp 0x517f330b, exception code 0xc0000005, fault offset 0x00e82ba0, process id 0x10f0, application start time 0x01cef03ce33dfeb0.

Yes I should submit a bug but the audio one looks like it had been done 3 times by what I read on the forum

#4

BTW if I got to windows task manager, 

1st  time i load project, memory usage is 349MB

when I reload its 470MB

then 592MB, 713MB, 834MB, 955MB, 1GB,1.19GB, 1.29GB (by now its taking ages to load)

Memory is not going up by much now after 3 more its 1,3GB . Its unbearable and about to crash. I only have 2GB so here lie the problem. 

A massive memory leak!

#5

The Graphics bug seems to be fixed with the Memory leak Fix so thanks for that.

still getting that horrid audio initialized bug though. If someone could tell me what in the Simulator program would cause the message to appear I might be able to help.

It has never appeared by a syntax or runtime error - I am assuming it really shouldnt happen. 

Stil, at least half the crashes have stopped.

#6

What daily build are you using?

I updated from 2013.2085 to 2013.2097 (and now for 2013.2099) and it is crashing several times on my MAC…

#7

Does this happen with your apps only or can you make it happen with our sample apps?

Thanks

Rob

#8

This tread is a good example of how forums are not good for helping engineering find problems.  It appears there are multiple problems here.  Its really hard to tell which version number you are running, what operating system you are running on, etc.

Engineering has fixed some problems this week on the Windows/Reloading/Memory Leaks issues.  These fixes of course won’t help starter’s on 2076 until the next public release.  It would be really helpful if each of you posted information that will help us:

Build #

OS

Open GL 2.0 compatible

Brief summary of the problem.

Thanks

Rob

#9

The Windows opengl changes and memory leak patches have been pushed into the newest public release. For the full list of changes, see the blog post below:

 

http://www.coronalabs.com/blog/2013/12/10/corona-sdk-new-public-release-2013-2100/

#10

I’ve had issues similar to this. When my projects are reloaded very rapidly (15-20 seconds between reloads), after about the 10th reload in succession, random graphics in the project will show as black rectangles instead of the actual graphic. It doesn’t break my graphics driver or anything, but I do need to shut down and restart Corona. 

I haven’t felt this was so dire I needed to file a bug report, but I wanted to let you know you’re not crazy, and this wasn’t just happening to you. I’m sure it has to do with the new release of the Corona Simulator; I haven’t encountered this in device testing.

Did you file a bug report? If not, I’d suggest you do so. That’s the best way for Corona to take a look at your issue.

http://developer.coronalabs.com/content/bug-submission

#11

Heres a windows log for the graphics crash if that helps

Faulting application Corona Simulator.exe, version 13.0.2090.0, time stamp 0x529409c2, faulting module atioglxx.dll, version 6.14.10.11672, time stamp 0x517f330b, exception code 0xc0000005, fault offset 0x00e82ba0, process id 0x10f0, application start time 0x01cef03ce33dfeb0.

Yes I should submit a bug but the audio one looks like it had been done 3 times by what I read on the forum

#12

BTW if I got to windows task manager, 

1st  time i load project, memory usage is 349MB

when I reload its 470MB

then 592MB, 713MB, 834MB, 955MB, 1GB,1.19GB, 1.29GB (by now its taking ages to load)

Memory is not going up by much now after 3 more its 1,3GB . Its unbearable and about to crash. I only have 2GB so here lie the problem. 

A massive memory leak!

#13

The Graphics bug seems to be fixed with the Memory leak Fix so thanks for that.

still getting that horrid audio initialized bug though. If someone could tell me what in the Simulator program would cause the message to appear I might be able to help.

It has never appeared by a syntax or runtime error - I am assuming it really shouldnt happen. 

Stil, at least half the crashes have stopped.

#14

What daily build are you using?

I updated from 2013.2085 to 2013.2097 (and now for 2013.2099) and it is crashing several times on my MAC…

#15

Does this happen with your apps only or can you make it happen with our sample apps?

Thanks

Rob

#16

This tread is a good example of how forums are not good for helping engineering find problems.  It appears there are multiple problems here.  Its really hard to tell which version number you are running, what operating system you are running on, etc.

Engineering has fixed some problems this week on the Windows/Reloading/Memory Leaks issues.  These fixes of course won’t help starter’s on 2076 until the next public release.  It would be really helpful if each of you posted information that will help us:

Build #

OS

Open GL 2.0 compatible

Brief summary of the problem.

Thanks

Rob

#17

The Windows opengl changes and memory leak patches have been pushed into the newest public release. For the full list of changes, see the blog post below:

 

http://www.coronalabs.com/blog/2013/12/10/corona-sdk-new-public-release-2013-2100/