well i upgraded to mac os high sierra but coronas latest version is saying it is not for mac os high sierra what do i do? i have corona 2017.3172
I’ve been running 2017.3160 on High Sierra for a while with no issues at all.
I have just downloaded 2017.3172 to see if your issue was reproducable.
It launches with no problems but as soon as I try to do anything at all with it - including just clicking on the window - it quits the simulator and then kicks me out of the OS back to the login screen. When entering my password to get back to the OS it will then relaunch finder. A couple of times it hasn’t quit the simulator but has still kicked me out, but because the simulator is still running every time I enter the password to go back into the OS it’s just kicking me straight back out again and I’ve had to pull the power and completely reboot.
Going back to previous release (3160) and it’s working fine.
I’ve not tried any of the releases between 3160 and 3172.
So I should use build 3160 too?
I upgraded to HIgh Sierra yesterday so I just downloaded 3172 and tried it and it worked as expected. Are there any messages in the console log? The mac’s “Console” that could give us a clue as to what’s happening?
Also if you can try 3171 or a couple of earlier versions that might help pinpoint the issue.
Rob
i think it’s working fine but it says:
2017-11-12 10:35:31.537 CoronaConsole[3524:496604] *** WARNING: Textured window <NSWindow: 0x7f8791421620> is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow’s -titlebarAppearsTransparent=YES instead
OK, ignore my reply. It’s looking like a problem with the computer itself as other apps have started doing the same thing.
Poop.
I get that warning too, but the simulator doesn’t crash or exhibit the other symptoms listed above.
Rob
ok thanks
I’m using macOS 10.13.1 and downloaded the latest daily build, 2017.3183 and Corona crashes immediately. No windows, no dialogs or messages. Completely unusable. Help!
With the last release version of Corona 2017.3135 I get the macOS Version Warning error message saying that 10.13 is not supported and pressing the “Continue” button gives me the simulator console but no launch/recents window.
Okay… So, not sure how to explain this, but after trying to launch the various versions of Corona a number of times, version .3183 is now launching with the welcome/launch window and console and I can launch my projects again. Not sure I understand why… but for now it’s working.
I remember one of our engineers having helped someone with the high sierra beta and somehow the app’s recent’s got corrupted. Clearing them seemed to solve the problem so maybe running 3135 reset your recents allowing the newer version to run.
Rob
I am also having many problems with recent Corona builds crashing immediately or hanging on Mac OS.
I’m on Mac OS Sierra (10.12.6) and recently upgraded to the new official version of Corona (3184) after using an older version for the last many months. Now Corona will typically start and work once, but then once you quit, it will no longer start again. Sometimes it just quits while trying to launch (and does not end up in Force Quit menu), other times it hangs trying to launch. Restarting the Mac seems to reset it, and then it will go back to working once. Tried latest daily build (3194) and got same results.
I am using the Corona Editor plug-in for Sublime if you think that might be an issue, but have tried to remove that with no change. Actually, oddly, if I run Corona from the Sublime add-in via Corona Editor > Run Project, Corona runs, with the integrated console output pane, but I can’t open the Corona Console Window… And in any case Corona will not launch on its own.
Having the same problem, note that I have a bunch of Macs here at work, and tried many combinations. The only broken combination so far is any new Corona version on High Sierra on a Mac Book Pro 2017 model, using a High Sierra on a Mac Air or older Mac Book Pro, has no issues. The OS totally crashes sometimes, screen becomes gibberish and then the machine resets. Like I say at work I have access to 3 Mac Book Pro 2017 model machines, and the same thing happens on all 3 machines, so it is not a random machine issue, but most likely an issue with the video board or something used for Mac Book Pro 2017 and Corona’s OpenGL implementation. Again there is no issue on other models of Macs, and unfortunately I don’t have a non-High Sierra Mac book pro, but before I updated to High Sierra to replicate anymore, older versions of Corona were working fine on the same Mac Book Pro 2017.
If Ansca engineers can get their hand on a Mac Book Pro 2017, I’m quite sure the issue will replicate, however like mentioned, the OS will crash, but I have no idea about error logs…
Hey guys,
Right now I am rocking a 15" 2017 Macbook Pro on High Sierra since release and have never met any crashes or some really weird stuff, like “screen becomes gibberish and then the machine resets”. Actually, this machine doesn’t show me any graphical glitches at all.
On my previous machines - 2016 13" Sierra and 2017 15" Sierra/High Sierra (don’t ask me why I’ve worked with so many recent macs :rolleyes: ) I’ve encountered some graphical issues/glitches, mostly on startup/login, but never on Corona Sim.
What I am saying is even though you’ve seen these issues on 3 different 2017 models, it’s not that every 2017 machine are having them, since my experience is completely opposite. Although, I must admit that some of the newer models may be having strange graphical glitches or crashes (and, sadly, ones are more than others for some mysterious reasons), but I am not quite sure that they are related to corona specifically or even opengl (but it surely possible). Not that I am defending Corona Sim (since I am working on it, hah), it’s just my personal experience.
If you have any use case that I can reproduce - feel free to share it here and I’ll be glad to test it and give my results. Can’t do anything more on this subject, since I am using any possible version of Corona Sim, like, all day every day, so I’m sure that if my machine were having some kind of issues, I’d stumbled upon them immediately.
I’ve set scaling option on retina 1440x900-like (that’s strange that Apple changed the default one to the one tick above that). Using a mac with an internal screen, 1080p screen and 4k screen in any combinations. GPU is Radeon 555. Not sure what other options may affect these issues.
contact801, btw, do the workflow on these 3 2017 machine of yours are the same? Like, apps, external monitors etc? We _might _find a hint there.
Not sure if it makes a difference, but all my MBP2017 are 13" High Sierra, models with the Touch Bar.
Anyways I don’t always get garbled screens right away. But it does crash in about a minute if I start doing things.
This happens with or without external displays, and besides that I have no keyboards, mouses or any other peripherals connected when this happens.
But as you also mention, I only have this issue on MBP2017 are 13" High Sierra, I’m quite sure the problem is actually with Apple and some driver or something, but as we all know Apple would never disclose such info, so it is up to developers to figure these things out. Not blaming Corona, I’ve been using it for a while, but just that I really don’t want to have to work on 2 machines (I currently use the simulator no problem on an old Mac Air).
However I’m worried that new people, with new macs, that encounter this sort of bug, would likely just give up and not even check the forums for help.
From your message, I had an idea, I unplugged my monitor, and reduced the screen resolution to 1024x640 and Corona Sim stopped crashing. Still getting occasional lost textures, but it didn’t crash.
Then increased the resolution to the default 1440x900, and wham! It crashed again. Looked up where I could find the kernel crash logs on my mac, and was able to replicate twice, so here I attached the logs as a zip.
One mentions that the thread causing the Panic was the Sim
BSD process name corresponding to current thread: Corona Simulator
Definitely there is some allocation error
*** Panic Report ***
panic(cpu 0 caller 0xffffff800209e69d): “a freed zone element has been modified in zone VM map entries: expected 0x53521cc9587ef0a but found 0x3f000a24a5d38c4e, bits changed 0x3a352be830546344, at offset 0 of 80 in element 0xffffff8053424c80, cookies 0x3f00113aa5eb9e56 0x53521cc95bae013”@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4570.31.3/osfmk/kern/zalloc.c:1120
Backtrace (CPU 0), Frame : Return Address
0xffffff81fec53620 : 0xffffff80020505f6
0xffffff81fec53670 : 0xffffff800217d604
0xffffff81fec536b0 : 0xffffff800216f0f9
0xffffff81fec53730 : 0xffffff8002002120
0xffffff81fec53750 : 0xffffff800205002c
0xffffff81fec53880 : 0xffffff800204fdac
0xffffff81fec538e0 : 0xffffff800209e69d
0xffffff81fec53940 : 0xffffff800209df70
0xffffff81fec53990 : 0xffffff800209c9b3
0xffffff81fec53ac0 : 0xffffff80020e0890
0xffffff81fec53ae0 : 0xffffff80020de832
0xffffff81fec53b50 : 0xffffff80020db6e5
0xffffff81fec53d30 : 0xffffff80020d93da
0xffffff81fec53e60 : 0xffffff800204429f
0xffffff81fec53ef0 : 0xffffff800215952d
0xffffff81fec53fa0 : 0xffffff8002002926
Hope this helps!
Immediate crash/hang happens consistently on both my iMac (late 2013) and MacBook Pro (late 2012), both Sierra 10.12.6.
I think contact801’s problem is likely different.
On Corona crashing/hanging immediately on launch, please note related thread:
https://forums.coronalabs.com/topic/71296-corona-simulator-wont-launch-and-crashing/
As I responded to Vlad in that thread, his command to disable the console window allows Corona to run, so it appears to be a problem related to the Console Window? Note that when the Sublime Corona Editor runs it with integrated Console Window, it will also run.
I just tried again, and this time got a GPU restart kernel panic.
Just to be clear, the project is a rather large game, that has worked fine for about a year, and when I build for iOS/Android there is no problem whatsoever, will try building for MacOS and see if that app crashes or if it just the sim next.
This thread might have a hint? The OP also has issues with a Mac Book Pro 2017, with 13" just like my machines, 15" might be ok, just 13" GPU has an issue?
Now, I have no idea if this is any help, but I noticed that before the GPU crashed twice, and rebooted (luckily the Machine stayed alive a bit before crashing totally) I noticed the following logs, which I can’t remember seeing before:
Jan 11 13:05:22.421 2018-01-11 13:05:22.421 Corona Simulator[1129:16549] *** WARNING: Method convertPointToBase: in class NSView is deprecated on 10.7 and later. It should not be used in new applications.
Jan 11 13:20:19.373 2018-01-11 13:20:19.372 Corona Simulator[1802:20578] *** WARNING: Method convertPointToBase: in class NSView is deprecated on 10.7 and later. It should not be used in new applications.