@vlads, as I wrote above, the Patched version did not crash - the graphics were still corrupted. The log included in my last post was for your Debug version.
https://pastebin.com/WaRGpkPZ
https://pastebin.com/DTXTggk1
Here is the crash logs when used Corona Simulator Debug.
bc_new_theway, what is your experience with “patched” one?
Here is the crash logs when used Corona Simulator Patched.
No thanks, I’m very good with my storage mechanism. What I wanted to explain is the way in which a software is used and for what it was created. Ex, if Corona SDK was created to run on Windows and Mac with its normal features, I do not see the reason for wanting to do things outside of the basic norm. I consider it unnecessary to have my new super computer, but to use it, I want to connect to the Tesla car that was put in orbit, use its radio and return to my computer in a fast and efficient way to listen Alien Radio 1040 when Windows or Mac have not created their computers to operate by default in that way. It is pure opinion. I’m writing with much respect, all of you has a lot of programming experience than I. Now, if it’s about not losing data, I can talk to you, from my facets as a music producer, graphic artist, as far as I am now I learned that the discs are not eternal, that they have to be changed even if they are in good condition, that you can not have the data stored on a single disc and pray that it will not be damaged. I have a good clone computer that I mount myself, has an external disk of 2T SSD that is where I keep everything, believe me everything, especially the musical content of all my work, my life, which at least every two years I sell half price and buy a new one to continue with the cycle. Also the most important thing for me is in a cloud that allows me to download, edit and upload from Windows or Mac. On the Mac I also have an external disk that contains everything, but the disk is for Mac and only for the Mac.
Everyone has their needs and their way of doing things differently from others.
If Corona SDK was created to work efficiently from the internal drive of each computer and an error occurs because some user wants to do things in a different way I consider that it is not the responsibility of the engineers to restructure an entire software because there is a crash when someone use a disc not compatible with a system from a third-party program that allows me to use it.
I repeat, I am saying this as an opinion and my words are with great respect for all who read them.
@dodi_games, you were clear and respectful. Everyone has their own reasons for configuring their setup, as do you. Thank you for your lengthy explaination, but it wasn’t necessary. If you want to discuss it further, please open a new topic - today, we discovered that @Vlads new patch no longer hard-crashes the system. The remaining issue is unrealted to our system configuration.
@Vlads, thank you for solving the hard-crash with the patch. Will the patch be made available in a daily build soon?
What else can we do to help you solve the graphic glitch/error?
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?