Hi again! I’ve tested the patched build and sadly I need to say that, almost on my MacBoook Pro 13, still freezes or kernel-panic the system. No luck here 
Can you share those crashes with us (using pastebin)?
Rob
I would… if it wasn’t because my system gets frozen 100% of the times, and I need to force shut down with the power button. I can share you the sequence of freezing: it starts with image corruption, and continues with complete system corruption. This is REALLY frustrating, takin in count that Corona is my main and only development environment
I’m unable to even share any crash report because after forced shut down, system only allows me to open previously opened apps.
Crash reports should be independent of what apps restart when the computer restarts. Look in ~/Library/Logs/DiagnosticReports/ to find them.
Rob
Hi Rob,
Maybe I didn’t make myself clear, but I haven’t any crash report in that folder because Corona itself doesn’t crash… is the whole OS X system: or crash (kernel panic) or directly (and most of the times) freezes and I can move only the mouse (and not in all cases).
@Vlads and @Rob, any word on when the ‘patch’ version will be in a daily build? And do you have a new version yet that fixes the graphics corruption crash on my MacBook Pro with Intel graphics?
We have a MBP that has the graphics corruption now and we are working on solving this. The “patched” version is not something we would recommend people using. It was just a test, and apparently, it didn’t fix it for everyone. Please give us some time to address this very hard to diagnose problem.
Rob
@Rob & @Vlads, just to be clear, the “patched” version does not prevent Corona from crashing. However, it DOES prevent it from causing a hard-crash, where it caused a reboot of my system. This is why I believe the “patched” version would be a worthwhile inclusion in a new daily build.
@Rob and @Vlads, any update on this? I am currently without my old system, so I find it just terrible that I cannot play and test my Corona App in the simulator on my new 2017 model Macbook Pro purchased “as new” from Apple on June 1, 2018. Being that others have reported these issues, too, it seems (but we’re not 100% certain) that this problem occurs on Mac’s running the integrated Intel graphics chip. Any update would be very much appreciated.
@Rob and @Vlads, today’s HARD CRASH on my New Macbook Pro has now occured in my new game that just went Beta. The hard crash caused a power surge which corrupted my main project hard disk, causing it no longer to be recognizable. I’ll have to send it out to be recovered.
Although my new game code and project is backed up, some important support files need the recovery. I haven’t been building my previous App on this system because of the problem reported in this thread, but I really didn’t expect this HARD CRASH to occur with the new game, as all was fine with it for 2 months now.
Had you implemented the code from the patch you sent me before, this HARD CRASH could have been avoided - as that version did result in a Corona crash, but it didn’t take down the system. My point is that Corona has had it within your power to implement the same code in that patch that could have prevented this. I don’t understand why whatever was changed, preventing the hard crash, was ignored from my previous reports above. There have been many recent builds, including a public build, and any one of them should have had the fixed-code you build in the patch.
Now, I am asking, as nicely as someone upset can ask, to please resolve this problem asap. My system runs NTFS for Mac and it is quality software, written by Paragon, and I’ve been using it flawlessly for more than 5 years. So please, don’t listen to anyone else that attempts to say that my use of NTFS is the cause. It is not. my point is, that if Corona didn’t crash, this wouldn’t have happened at all.
Please accept my apology for my late-night rant. I still love CoronaLabs, your team and your software. It’s a late evening here in Honolulu and I’m unable to work due to this issue.
Hello! We got a laptop which also have this bad behaviour and localized the issue. We are working on it now. There was some other urgent stuff we had to deal with and this project was paused.
We’re back on it as of state of now.
[member=‘troylyndon’], if it works for you, you can use “patched” version for development for now. It is not much different than public build. Fix was very raw and probably doesn’t fix the issue at it’s core.
we’re on it, however, this bug proven to be extremely difficult.
@vlads, I believe enough time passed the patched version doesn’t suppose the latest xCode or iOS version. Is it difficult to prepare another version until you can include the patch in a daily build?
The patched version is from July 18, which is using Xcode 9.4 and the iOS 11.4 SDK which are the latest.
Rob
@Rob, thank you! So, you think it should be okay to use this version to update my existing app or release a new app with the patched version?
Vlad seems to think it’s okay. I’m just confirming that there are not any new iOS/Xcode updates since that release version. I don’t know what was changed or how it affects you. I wish I could be more useful here.
I doubt the change in patched effects builds, but more something that may help keep the simulator from crashing on your MBP.
Rob
My bad. You can use patched to develope. To build your app please use latest daily build.
@Rob, just for clarity, the patch does not prevent Corona from crashing. But instead of a hard crash, the patch brings up the crash in a normal window without taking down the system. So whatever the change is in that patch, it is the difference between causing a hard crash on the Intel graphics models (like mine) and not. Of course, I’m making an educated guess based upon the Intel graphics comments from other contributors to this thread. THANK YOU for your attention to this.
Yes, it is seems to be happening exclusively on new MBP with Intel Iris graphics. Something is bad in driver, which goes wild and corrupts memory, causing crash as a consequence. It is extremely hard to fix, because bug is very random, and seemingly doens’t produce any errors inside the app.
Again, if Patched version works for you, use it for development. But do not submit builds made with it to the Store. Use daily build or public build for that. Like, you can open project and build, right?
@Vlads, myself and one other poster here were able to provide you with 2 examples that cause graphic corruption EVERY TIME. If you solve those corruptions, the crash will probably not occur. Do you need help from us to repost?
Hey guys. I was debugging the issue. Here’s what I want to ask you to do:
-
Start Simulator
-
Select Window → View As → Borderless → Windows Phone 480 x 800
(really, anything without iPhone/iPad in it would do)
- Try some other projects