Using Corona with new release of OS X Yosemite.

Now that Yosemite has been released, I thought it would be useful to have a post where people can see what the current situation is regarding using Corona on it. I for one would prefer to see if it works ok before I upgrade.

Could anyone who has used it (or someone from Corona) let us know if everything is working ok?

And the same for Enterprise would be useful.

I just upgraded to Yosemite and Corona doesn’t work there (I have latest public release), it says “Couldn’t launch Corona Simulator, fatal error occured” (see the screenshot) screen.png

…I don’t see any attachment in your post.

I’ve been using Corona (Pro + Enterprise) on Yosemite for about a month now (and also released apps to the Apple App Store) without any issues.

@Nyxbull

I’m not sure if your issue may be with the public release as I’m using the latest Daily Build.

After installing Yosemite, I have been prompted to install some legacy JAVA runtime, that I have done.  I also got a message about open GL things being disabled due to a bug in the beta version of OS-X.

I’am a Basic user, so don’t have access to any daily builds

Yes, the Java runtime is necessary (the same was needed for Mavericks).

The disabled OpenGL warnings were put in place because of incompatibility in the early Yosemite betas.

These warnings are removed in later Corona daily builds.

A reply from Corona stuff on Yosemite and public 2393 Corona build would be welcome on this subject. Thanks. St

I solved my issue just by deleting Corona and installing it again, got the same warning message about OpenGL as murrough.obrien but everything is working now

Seems to be fine, though I am using latest DB

Earlier builds of Yosemite had an OpenGL bug that prevented Corona SDK from running on it.  The release version does not have this issue.  I know that in some daily builds (2362), we put in some protections around the bug which disabled native features while Apple solved this, but it should have been removed (build 2437).  The public build has these protections built in.  You should be able to click past the dialog, but these native features will still be disabled.  Any daily build after 2437 and later should be fine.

Now, Yosemite uninstalls Java 6 which Corona SDK needs.  There should be a link on the message box about needing Java 6 that says “more info”.  This should take you to a place where you can re-install it.

Rob

I installed Yosemite today and corona started fine for me. But I noticed a major drop in framerate, anyone else experinced this? I had no problems before. Guess my macbook air is starting to get a little old, but if I had know this I would not have updated the osx since I mostly use it for programming and other things related to that.

Seems like Yosemite uses a ton of ram. It’s using 100% of my 12gb of ram doing nothing, Mavericks was using about 6gb tops during my work flow. Not sure if this is a change in their memory handling or a bug, but i have had problems.

I have had several freeze ups and crashes, and apps (apples and third party mac apps) using over 60gb of ram (according to activity monitor), which means you get hdd trashing.

I’m seriously contemplating going back to Mavericks, and waiting a few months before upgrading again.

Over 60gb of RAM? How much RAM do you have?!

So when we going to get a public release that matches the current manufacturers OS versions then.  i’m going to have to go back to OS X which is a pain.  Its not as if Corona did not know this was coming!

12gb :wink: the rest was being taken away using swap (from ssd), aka virtual memory.

Crazy stuff

@euphoriacorona

That sounds very weird. I’ve been using Yosemite since GM candidate 1 and I haven’t seen this behavior at all. Yosemite has been running very smooth with no crashes or performance issues at all for me. I’ve even been doing quite intensive video rendering with FinalCut Pro without issues.

The memory pressure reported by Activity Monitor is in the green all the time. My swap used is currently 45 MB.

The only time the memory pressure turns yellow (sometimes) is when I start VMWare and run a Windows 8 VM with 2GB RAM allocated which isn’t surprising since I only have 8GB total.

I’m on an iMac 27" (late 2011) with 8GB RAM, 3.4GHz Intel Core i7

Yeah, it is. How much memory is in use on your system right now?

If OS X consumes all the ram and allocs it when needed, that’s fine… But i would love to be able to see how much of that allocated ram is actually being used. Not a big fan of the pressure graph

From this you can see that 7.98 GB is in use (which is the sum of all the memory on the right hand side of the graph). 

2.34 GB for Apps 

2.72 GB for File cache 

1.15 GB Wired memory  (can’t be swapped)

1.76 GB Compressed

======

7.97 GB

The virtual memory isn’t usually much to take notice of since it’s an indication of how much memory the apps have asked to use, and not a value of actual memory used.

Interesting. So it’s allocated all of your ram too. I’m just installing Mavericks again to compare, as i am sure it didn’t work like this, but my memory could be hazy. Will report back :wink:

Edit: Using 6.3gb on Mavericks under the same conditions

In any case my system is running as smooth as can be with only 8 GB RAM.

I’ll be upping the RAM to 16 or 32GB together with a new iMac with 5K Retina Display when it has passed the ECC certification tests here in Korea. Rumor has it that it’s going to be by the end of the month. Gotta’ love that display!