Just open the dialog and then switch few times to another application ( alt-tab). I have also attached a small application you can run. This is a Java crash on Mac OS Mojave, the stack trace is below. This is a major bug for all JavaFx applications running on MacOs. I am thrilled.The bug I report seems to be fixed in JDK-8211304, but only in Java 12. Once the Java story improves in Apple silicon, I will write about it. The Java Virtual Machine will need to be recompiled for Apple Silicon to fully utilize its power, but Java based applications should continue to run as expected on both Intel and Apple Silicon hardware. The Java runtime support will run under Rosetta 2 which will translate Intel compiled code to run on Apple Silicon. The exciting thing is that Java builds are not taking full advantage of the transition. Macbook Air M1 will get you similar Java build times for current top of the line Macbook Pros.The Macbook Air M1 smokes old Macbook Pros.My 2017 iMac Pro, a powerhouse, still beats an Macbook Air M1.I explicitly disabled several features (Build Cache, Daemon) which make Gradle builds much faster. Neither, it is intended to showcase of Gradle's performance. However, I was not able to get the Gradle Profiler to run with the M1 computer.ĭon't consider this post as a measurement Micronaut security's build performance. These benchmarks should have been calculated with the Gradle Profiler. Java builds are fast in a Macbook Air M1. The goal of the post is to put in numbers my feelings. By using the -parallel switch, you can force Gradle to execute tasks in parallel as long as those tasks are in different projects. Yet Gradle will only run one task at a time by default, regardless of the project structure (this will be improved soon). Most builds consist of more than one project and some of those projects are usually independent of one another. I use Gradle Parallel execution with -parallel flag. I ignore tests which required Docker (which does not run with Apple M1), hence the argument -Dtestcontainers=false. I skip the task dependencyUpdates as it may add inconsistency to the test.

For the same reasons as in the previous item, to compare different machines in the fairest way. I disable the Gradle Daemon with -no-daemon. I use -no-build-cache because I want to have an easy way to compare between machines. I run the Gradle build task which compiles the code, runs the tests and checksytle. OpenJDK 64-Bit Server VM 25.275-b01 (mixed mode) OpenJDK Runtime Environment 1.8.0_275-b01Ī Inc. I compare an iMac Pro, Macbook Pro, Macbook Air 2020 M1 for a common Gradle Java build.

Java jdk mac os mojave