Each time I close the simulator on Windows 7 I see the attach alert appear. Should this be happening or am I just lucky?
I have never got this kind of message:) I use Windows 7 64-bit and Corona v. 2017.3184
I get 10-20 sim crashes per day - normally on project reloading
Crazy.
I wouldn’t think you should be seeing that. I don’t know what questions to ask you to help our engineers figure this out. I’m not sure we have any Win7 machines to test it on. Is there anything in the Corona console log that might clue us in?
Rob
I’ll have a look when I get back to work (Monday) - I had meant to check the system log but forgot…
I really hope this helps:
Faulting application name: Corona Simulator.exe, version: 18.0.3223.0, time stamp: 0x5a86be52 Faulting module name: ntdll.dll, version: 6.1.7601.24000, time stamp: 0x5a49962f Exception code: 0xc0000005 Fault offset: 0x0002e081 Faulting process id: 0xa74 Faulting application start time: 0x01d3a972e8a4c3fa Faulting application path: C:\Program Files (x86)\Corona Labs\Corona SDK\Corona Simulator.exe Faulting module path: C:\WINDOWS\SysWOW64\ntdll.dll Report Id: 4727e4ca-1566-11e8-aecf-d481d77c1fd1Mine are slightly different and on Windows 10
Faulting application name: Corona Simulator.exe, version: 18.0.3200.0, time stamp: 0x5a5895cb Faulting module name: MSVCR120.dll, version: 12.0.40649.5, time stamp: 0x56bc018f Exception code: 0xc0000409 Fault offset: 0x000a7746 Faulting process id: 0x2734 Faulting application start time: 0x01d3a8bcc468d5c3 Faulting application path: C:\Program Files (x86)\Corona Labs\Corona\Corona Simulator.exe Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll Report Id: 1ca4ccdf-e7d2-4006-be56-02017abae25cI’ll send this to Engineering and see if they have any thoughts on this.
Rob
@horacebury, can you try a few things…
What happens if you just start the simulator and then exit?
What happens if you just start the simulator, load the HelloWorld sample and then exit?
Do you have another PC you can try it on?
Thanks
Rob
On this Windows 7 (which is an enterprise machine at work) both of those options give the same result, as you see above.
I will see if one of my colleagues has a Windows 7 machine to test on, but I’m the only Corona dev around here.
i had missed/overlooked this post.
@sysop feel free to merge/delete my other post - it’s same symptom (exc 0xc0000409, at 0x000a7666, in MSVCR120.dll)
I have never got this kind of message:) I use Windows 7 64-bit and Corona v. 2017.3184
I get 10-20 sim crashes per day - normally on project reloading
Crazy.
I wouldn’t think you should be seeing that. I don’t know what questions to ask you to help our engineers figure this out. I’m not sure we have any Win7 machines to test it on. Is there anything in the Corona console log that might clue us in?
Rob
I’ll have a look when I get back to work (Monday) - I had meant to check the system log but forgot…
I really hope this helps:
Faulting application name: Corona Simulator.exe, version: 18.0.3223.0, time stamp: 0x5a86be52 Faulting module name: ntdll.dll, version: 6.1.7601.24000, time stamp: 0x5a49962f Exception code: 0xc0000005 Fault offset: 0x0002e081 Faulting process id: 0xa74 Faulting application start time: 0x01d3a972e8a4c3fa Faulting application path: C:\Program Files (x86)\Corona Labs\Corona SDK\Corona Simulator.exe Faulting module path: C:\WINDOWS\SysWOW64\ntdll.dll Report Id: 4727e4ca-1566-11e8-aecf-d481d77c1fd1Mine are slightly different and on Windows 10
Faulting application name: Corona Simulator.exe, version: 18.0.3200.0, time stamp: 0x5a5895cb Faulting module name: MSVCR120.dll, version: 12.0.40649.5, time stamp: 0x56bc018f Exception code: 0xc0000409 Fault offset: 0x000a7746 Faulting process id: 0x2734 Faulting application start time: 0x01d3a8bcc468d5c3 Faulting application path: C:\Program Files (x86)\Corona Labs\Corona\Corona Simulator.exe Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll Report Id: 1ca4ccdf-e7d2-4006-be56-02017abae25cI’ll send this to Engineering and see if they have any thoughts on this.
Rob