top | item 25802458 (no title) posedge | 5 years ago Yeah about that, do you have some insight on why the X background daemons are always 'incompatible' and gradle launches up new ones? discuss order hn newest gddhn|5 years ago Being new to Gradle, I used to run into this same issue. In one of the projects I use, I happened to find this comment, in github, which helped me fix the issue https://github.com/quarkusio/quarkus/issues/10454#issuecomme...So increasing the default max heap size of the gradle build helped fix the issue https://github.com/quarkusio/quarkus/pull/10508/files. benibela|5 years ago And how could I make sure that the gradle I start on the command line and the gradle started by Android Studio use the same daemon?
gddhn|5 years ago Being new to Gradle, I used to run into this same issue. In one of the projects I use, I happened to find this comment, in github, which helped me fix the issue https://github.com/quarkusio/quarkus/issues/10454#issuecomme...So increasing the default max heap size of the gradle build helped fix the issue https://github.com/quarkusio/quarkus/pull/10508/files. benibela|5 years ago And how could I make sure that the gradle I start on the command line and the gradle started by Android Studio use the same daemon?
benibela|5 years ago And how could I make sure that the gradle I start on the command line and the gradle started by Android Studio use the same daemon?
gddhn|5 years ago
So increasing the default max heap size of the gradle build helped fix the issue https://github.com/quarkusio/quarkus/pull/10508/files.
benibela|5 years ago