I recently upgraded to mac OS X Lion and installed Xcode 4.1. I have noticed, at least on my machines, that Xcode, more specifically libclang.dylib, is leaking a lot of memory (ex. see screen shot of Instruments). I also did a fresh install and reinstalled Xcode and it does the same thing. I am wondering if other people are having this problem and is there a way I can temporarily patch this (ex. disable clang, etc.)? thanks in advance
Related
I currently have a windows laptop with an intel i5. I am looking to upgrade to an M1 mac. Emulation isn't a problem for me(Virtualization is slower on ARM). Can any early adopter let me know if it is fast enough for basic android development and some Xcode?
Available on Android Studio Arctic Fox (Beta)
The Beta version (Arctic Fox Beta 4) now has Apple Silicon support, so you can download it from Android Studio download archives. Look for, for example: Mac (Apple Silicon): android-studio-2020.3.1.19-mac_arm.zip (955253378 bytes). Don't use jetbrains toolbox because it is bit buggy, it downloaded an outdated version of Android Studio. I've noticed its also a day late on releases.
Serious performance issues (before May 2021)
I've tried to use Android Studio for the past couple of months, and to me, it is unusable, let alone at parity with running it on Intel. I've always been on the Canary version too. I keep telling myself the M1 is faster, but I in reality I only notice speed reduction and freezes when compared to MacBook Pro 16" 2020 2.3GHz 8‑core Intel Core i9 or my Intel i7-9700K Hackintosh. I also use a physical device to dedicate more mac resources to the IDE.
Very slow indexing/ navigation around the code base
Very slow typing and clicking sometimes (general lag)
Random freezes which require app restart
The compile times are the least of my worries (see bottom section).
Unfortunately, it is still very slow. Here I measure how long ./gradlew assembleDebug takes after a warm up of the same (./gradle assembleDebug):
MacBook Pro 2.3GHz 8‑core Intel Core i9 VS. Mac M1 Mini
3 minutes and 1 second VS. 4 minutes and 46 secinds
CPU Temperatures: 88 to 92C(+hot air blowing out 😅) VS. 41 to 45C
M1 chips are cool (in a temperature sense), but currently slow. I'll update when a Apple Silicon optimized Android Studio comes out.
I've been using a Macbook Pro with M1 for Android development in Android Studio for the past few days. It does feel a little slow at times, but the fact that it was never an incredibly smooth application to begin with (on my old 13" MacBook Pro anyway) means it's not much different. Also, since it's under Rosetta 2 at the moment I'm pretty happy with the performance.
I'd say if you're not working on anything critical then it's fine. However, I'd still be wary of recommending it to people who need a reliable solution for work and if you need the Android emulator you're out of luck completely as you need to rely on a dedicated device.
It's definitely okay for basic Android development. I've had a few instances where it has randomly frozen on me and I've had to do a force quit. And it doesn't particularly feel like it is quicker than the 2015 MacBook Pro I was running it on before(!) It is, however, very quiet (no fan!) and hopefully now that IntelliJ has been ported we can see a dedicated M1 version of Android Studio soon.
I have the macBook air with m1 chip and it is fast every where but for android studio just forget about it , it crash every 1h especially when I create new class
or a new activity , like at least every 1h you will have a crash so you have to force quit the app and open it again .
Is anyone else using NDK with the M1?
I have two Android apps that I use Android Studio for. I tried both on my new M1 Mac mini.
One, relatively simple and Java only, builds fine.
The second has Java and C code (uses the NDK). Building it fails with a crash of Android Studio.
As a result of this, I'm having to develop on my legacy Intel MacBook Pro.
To use it, you need to download from: https://developer.android.com/studio/archive and look for Mac (Apple Silicon), and you need to use Gradle 6.9-rc1+ .
Source: https://androidstudio.googleblog.com/2021/04/android-studio-arctic-fox-canary-15.html
For compilation time reduce by 4, I found the best solution here.
We have in our project more than 1200 unit tests, the time to execute all this tests was 7-8 minutes, now with this JDK it only takes 1 minute and a half.
Best solution from Elye.
I need help on this please..
I have installed JME sdk 3 in windows 7 professional 32 bit system
I have jdk also already installed.
When i try to start JME platform using the icon in start menu or the the jmonkeyplatform.exe file in program files/jmonkeyplatform/bin , it lauches the startup logo. It says reading,loading modules, turning on modules and then starting modules. But after that it suddenly disaperars. Nothing happens , no error msg.
I have nvidia graphics card in my system
What do I have to do? Please help. I also uninstalled and re-installed. Is it the problem with version of jme? Or some problem with with my graphics card setting?
Please guide..
Thanks in advance.
Finally its working now.
I uninstalled the jmonkey platform and downloaded another version from here
http://jmonkeyengine.org/downloads/ --->jMonkeyEngine 3 SDK – Windows (32-bit)
I installed it and it worked.
May be the earlier JME 3 was not suitable for my system.
Thanks anyway..
www.shankysportal.com
I am using version 1.9.0 of the REDHAWK IDE on CentOS 6.5 and ran software updates today, made up of OpenJDK updates.
Before the updates, I was able to see the sandbox and chalkboard in the IDE. When I opened the IDE a little while after the updates, the sandbox was gone.
I tried installing Java SE JRE version 1.8.0_05 and restarting REDHAWK IDE without success.
I then tried a fresh IDE installation, which successfully showed the sandbox for two different times starting the IDE. Although, after being closed for an hour or so, the sandbox went missing again.
Does this sound like a java issue? If not, is the IDE breaking itself in some way?
Note that during the time of REDHAWK inactivity I was only using a word processor and a web browser.
Edit: Prior to the updates I had installed the newest GNU HAWK components and was able to load various GNU HAWK components onto the chalkboard with the sandbox still showing up.
I had the same issue, and ended up fixing it by commenting out the following line in the eclipse.ini file:
#-Dorg.omg.CORBA.ORBClass=org.jacorb.orb.ORB
For other people looking at this, I went through the basic example in the Getting Started and the plot window would flash and go away. It is related to that line in the accepted answer.
I need to deploy a JavaFX2.2 application on Mac machines. OS X 10.7 or later are fine with Java 7u7. What about OS X 10.6? Do we have any workaround? I think 10.6 can update upto Java 6u35 and somewhere I read 2.1 & 2.2 can run with 6u26 or later (However there are no support though which is ok).
Can someone please help me to accomplish this? Can we just download standalone JFX2.2 runtime from somewhere and put it on OSX10.6? Or any other alternative option? Is there a way we can copy/package 2.2 runtime along with the app itself?
Please help.
Is there a way we can copy/package 2.2 runtime along with the app itself?
Yes, see the documentation on self-contained application packaging which is supported on OS X 10.7+ and includes JavaFX 2.2+ and jre7u6+.
What about OS X 10.6?
Quote from an oracle forum thread by the JavaFX lead regarding Snow Leopard support and JavaFX 2.2:
FWIW, there are in fact some APIs we use from Lion that aren't on Snow Leopard. Also, Apple only supports the current release of the OS - 1 (so now it would be Lion and Mountain Lion), and for deployment we needed special hooks. The thought was that it didn't make sense to support versions of the Mac OS that Apple themselves didn't support any longer.
Some of the early developer builds of JavaFX (2.0/2.1) did run on Snow Leopard, but they were only early development builds and not production ready, plus, I don't think the license on those builds allow you to use them in production code. I don't think these early 2.0/2.1 development builds are distributed by Oracle anymore.
When JavaFX is fully open sourced, you might be able to undertake an effort to backport it to Snow Leopard, but by then it probably wouldn't be worth it.
As a hack, you could try adding the JavaFX runtime bundled in jre7u7+ to an Apple Java6u35 and see if you can run an app - but this would be a totally unsupported configuration likely to break and may also have distribution licensing issues.
Reasons why mac does not work with javafx.. currently
From: https://blogs.oracle.com/henrik/entry/oracle_jdk_and_javafx_sdk
Quote:
Note that support on Mac is for development only; e.g. we don't expect your Mac to be running a business critical server-side application...
Context: JavaFx is still in development on mac since java7, full on support was expected at java 8. Java 8 will be real eased september
From: http://www.oracle.com/technetwork/java/javafx/downloads/supportedconfigurations-1506746.html
Quote:
MacOs is only supported in 10.7.3 or greater (Mac OS X Lion, the second newest operating system)
Context: Stating JavaFx supported configurations. There are many browsers where JavaFx will not work!
From: http://docs.oracle.com/javafx/
Quote:
JavaFX applications run on a desktop. On Windows, they also run in a browser, and over the web.
Context: This with following quote implies only developmental progress on macOS
From: http://ed4becky.net/homepage/javafx-from-the-trenches-part-2-its-not-always-about-the-sex/?rcommentid=26916&rerror=incorrect-captcha-sol&rchash=35499a8f4e0544f950435495d20b0cf1#commentform
Quote:
Turns out there is a bug in the ChoiceBox – JIRA RT-26837 I talk about on the JavaFX2 Forum. It got the attention of Jonathan Giles at Oracle, and he escalated the fix, but it won’t be out until Java8 is released.
Context: There are still a lot of bugs that will keep you from success on mac!
I bought a new Retina MacBook Pro to develop for iOS with MonoTouch.
It is extremely frustrating that, probably because it is built on Gtk#, MonoDevelop is very blurry.
I can cope with blurry UI but I can't read or write code because it hurts my eyes.
What is the current status of Retina support in Gtk# and MonoDevelop?
Is there any (experimental) compile flag at least to enable proper code rendering?
If I want to contribute, which component is in charge of this? Is it Gtk# or Gtk itself?
Update
This has been fixed as of MonoDevelop 3.0.4:
Other improvements and bug fixes
Fixed rendering on MacBook with retina display
So just go and download it.
Workaround for Older Versions (and other apps, too)
There is a temporary work around I used for WebStorm that worked well. It should work for MonoDevelop too.
You can use that in the mean time until the Xamarin folks get an update to MonoDevelop out.
Here it goes:
Locate MonoDevelop in Applications and click Show Package Contents
Open Contents/Info.plist in any editor and add this after opening <dict>:
<key>NSHighResolutionCapable</key>
<true/>
Copy and paste MonoDevelop app bundle, delete the old one and rename the new one back to MonoDevelop. This will flush system caches.
You will notice that MonoDevelop.app info now has Low Resolution option unchecked and the code renders smoothly.