[jira] [Commented] (NETBEANS-3041) NetBeans gradle invoker not honouring org.gradle.jvmargs
[ https://issues.apache.org/jira/browse/NETBEANS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006234#comment-17006234 ] Shevek commented on NETBEANS-3041: -- 30 second code review looks a lot better, I see a break statement where I expected one, thank you again. > NetBeans gradle invoker not honouring org.gradle.jvmargs > > > Key: NETBEANS-3041 > URL: https://issues.apache.org/jira/browse/NETBEANS-3041 > Project: NetBeans > Issue Type: Bug >Reporter: Shevek >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, pull-requests-available > Fix For: 11.3 > > Time Spent: 4h 20m > Remaining Estimate: 0h > > cat .gradle/gradle.properties > org.gradle.jvmargs=-Xmx8192m -XX:+PreserveFramePointer > This property is not honoured by NetBeans when it starts a Gradle daemon, so > I end up with a Gradle daemon using the "default" amount of RAM, which on > some machines is too little, and on some is too much (it's 25% of system RAM). > I'm guessing this is because it's loaded by the wrapper, not the daemon, > because other properties like org.gradle.daemon.idletimeout=36 are > honoured by NB's gradle daemon. > The other effect of not loading that property is that I get multiple gradle > dameons running, each consuming 16Gb of RAM, because they're "incompatible", > so fixing this will save me about 16Gb of RAM per system. > I'm a bit shaky on this bug report, but ... I think this is what's going on. > (footnote: oh dear, Shevek broke something again, what on earth is that idiot > doing with NetBeans and why can't Shevek just behave like a "normal" > developer :D :D) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3041) NetBeans gradle invoker not honouring org.gradle.jvmargs
[ https://issues.apache.org/jira/browse/NETBEANS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006233#comment-17006233 ] Shevek commented on NETBEANS-3041: -- Thank you. For clarity, I did not actually reproduce this bug in 11.2, I discovered it by doing code review of the PR on github, but it jumped out at me. Also, I know for a fact that if I _did_ switch to 11.2, I would hit the bug as several of the circumstances above apply to our organization. > NetBeans gradle invoker not honouring org.gradle.jvmargs > > > Key: NETBEANS-3041 > URL: https://issues.apache.org/jira/browse/NETBEANS-3041 > Project: NetBeans > Issue Type: Bug >Reporter: Shevek >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, pull-requests-available > Fix For: 11.3 > > Time Spent: 4h 20m > Remaining Estimate: 0h > > cat .gradle/gradle.properties > org.gradle.jvmargs=-Xmx8192m -XX:+PreserveFramePointer > This property is not honoured by NetBeans when it starts a Gradle daemon, so > I end up with a Gradle daemon using the "default" amount of RAM, which on > some machines is too little, and on some is too much (it's 25% of system RAM). > I'm guessing this is because it's loaded by the wrapper, not the daemon, > because other properties like org.gradle.daemon.idletimeout=36 are > honoured by NB's gradle daemon. > The other effect of not loading that property is that I get multiple gradle > dameons running, each consuming 16Gb of RAM, because they're "incompatible", > so fixing this will save me about 16Gb of RAM per system. > I'm a bit shaky on this bug report, but ... I think this is what's going on. > (footnote: oh dear, Shevek broke something again, what on earth is that idiot > doing with NetBeans and why can't Shevek just behave like a "normal" > developer :D :D) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3041) NetBeans gradle invoker not honouring org.gradle.jvmargs
[ https://issues.apache.org/jira/browse/NETBEANS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005050#comment-17005050 ] Laszlo Kishalmi commented on NETBEANS-3041: --- The new PR got merged, I hope it works good now. > NetBeans gradle invoker not honouring org.gradle.jvmargs > > > Key: NETBEANS-3041 > URL: https://issues.apache.org/jira/browse/NETBEANS-3041 > Project: NetBeans > Issue Type: Bug >Reporter: Shevek >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, pull-requests-available > Fix For: 11.3 > > Time Spent: 4h 20m > Remaining Estimate: 0h > > cat .gradle/gradle.properties > org.gradle.jvmargs=-Xmx8192m -XX:+PreserveFramePointer > This property is not honoured by NetBeans when it starts a Gradle daemon, so > I end up with a Gradle daemon using the "default" amount of RAM, which on > some machines is too little, and on some is too much (it's 25% of system RAM). > I'm guessing this is because it's loaded by the wrapper, not the daemon, > because other properties like org.gradle.daemon.idletimeout=36 are > honoured by NB's gradle daemon. > The other effect of not loading that property is that I get multiple gradle > dameons running, each consuming 16Gb of RAM, because they're "incompatible", > so fixing this will save me about 16Gb of RAM per system. > I'm a bit shaky on this bug report, but ... I think this is what's going on. > (footnote: oh dear, Shevek broke something again, what on earth is that idiot > doing with NetBeans and why can't Shevek just behave like a "normal" > developer :D :D) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3041) NetBeans gradle invoker not honouring org.gradle.jvmargs
[ https://issues.apache.org/jira/browse/NETBEANS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004507#comment-17004507 ] Laszlo Kishalmi commented on NETBEANS-3041: --- [~arren] first of all, your bug reports are appreciated. At least it seems somebody is using NetBeans with Gradle. > NetBeans gradle invoker not honouring org.gradle.jvmargs > > > Key: NETBEANS-3041 > URL: https://issues.apache.org/jira/browse/NETBEANS-3041 > Project: NetBeans > Issue Type: Bug >Reporter: Shevek >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, pull-requests-available > Fix For: 11.2 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > cat .gradle/gradle.properties > org.gradle.jvmargs=-Xmx8192m -XX:+PreserveFramePointer > This property is not honoured by NetBeans when it starts a Gradle daemon, so > I end up with a Gradle daemon using the "default" amount of RAM, which on > some machines is too little, and on some is too much (it's 25% of system RAM). > I'm guessing this is because it's loaded by the wrapper, not the daemon, > because other properties like org.gradle.daemon.idletimeout=36 are > honoured by NB's gradle daemon. > The other effect of not loading that property is that I get multiple gradle > dameons running, each consuming 16Gb of RAM, because they're "incompatible", > so fixing this will save me about 16Gb of RAM per system. > I'm a bit shaky on this bug report, but ... I think this is what's going on. > (footnote: oh dear, Shevek broke something again, what on earth is that idiot > doing with NetBeans and why can't Shevek just behave like a "normal" > developer :D :D) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3041) NetBeans gradle invoker not honouring org.gradle.jvmargs
[ https://issues.apache.org/jira/browse/NETBEANS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921186#comment-16921186 ] Laszlo Kishalmi commented on NETBEANS-3041: --- I can confirm this. We've got a PR, so this is in progress. > NetBeans gradle invoker not honouring org.gradle.jvmargs > > > Key: NETBEANS-3041 > URL: https://issues.apache.org/jira/browse/NETBEANS-3041 > Project: NetBeans > Issue Type: Bug >Reporter: Shevek >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-requests-available > Time Spent: 10m > Remaining Estimate: 0h > > cat .gradle/gradle.properties > org.gradle.jvmargs=-Xmx8192m -XX:+PreserveFramePointer > This property is not honoured by NetBeans when it starts a Gradle daemon, so > I end up with a Gradle daemon using the "default" amount of RAM, which on > some machines is too little, and on some is too much (it's 25% of system RAM). > I'm guessing this is because it's loaded by the wrapper, not the daemon, > because other properties like org.gradle.daemon.idletimeout=36 are > honoured by NB's gradle daemon. > The other effect of not loading that property is that I get multiple gradle > dameons running, each consuming 16Gb of RAM, because they're "incompatible", > so fixing this will save me about 16Gb of RAM per system. > I'm a bit shaky on this bug report, but ... I think this is what's going on. > (footnote: oh dear, Shevek broke something again, what on earth is that idiot > doing with NetBeans and why can't Shevek just behave like a "normal" > developer :D :D) -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3041) NetBeans gradle invoker not honouring org.gradle.jvmargs
[ https://issues.apache.org/jira/browse/NETBEANS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918330#comment-16918330 ] Shevek commented on NETBEANS-3041: -- pstree confirms, the gradle daemon which is missing the -Xmx is a child of netbeans. > NetBeans gradle invoker not honouring org.gradle.jvmargs > > > Key: NETBEANS-3041 > URL: https://issues.apache.org/jira/browse/NETBEANS-3041 > Project: NetBeans > Issue Type: Bug >Reporter: Shevek >Priority: Major > > cat .gradle/gradle.properties > org.gradle.jvmargs=-Xmx8192m -XX:+PreserveFramePointer > This property is not honoured by NetBeans when it starts a Gradle daemon, so > I end up with a Gradle daemon using the "default" amount of RAM, which on > some machines is too little, and on some is too much (it's 25% of system RAM). > I'm guessing this is because it's loaded by the wrapper, not the daemon, > because other properties like org.gradle.daemon.idletimeout=36 are > honoured by NB's gradle daemon. > The other effect of not loading that property is that I get multiple gradle > dameons running, each consuming 16Gb of RAM, because they're "incompatible", > so fixing this will save me about 16Gb of RAM per system. > I'm a bit shaky on this bug report, but ... I think this is what's going on. > (footnote: oh dear, Shevek broke something again, what on earth is that idiot > doing with NetBeans and why can't Shevek just behave like a "normal" > developer :D :D) -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3041) NetBeans gradle invoker not honouring org.gradle.jvmargs
[ https://issues.apache.org/jira/browse/NETBEANS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918183#comment-16918183 ] Shevek commented on NETBEANS-3041: -- Reason I think this is happening: Inspecting the JVM args of each running gradle daemon using visualvm. I suppose I should check pstree as well. > NetBeans gradle invoker not honouring org.gradle.jvmargs > > > Key: NETBEANS-3041 > URL: https://issues.apache.org/jira/browse/NETBEANS-3041 > Project: NetBeans > Issue Type: Bug >Reporter: Shevek >Priority: Major > > cat .gradle/gradle.properties > org.gradle.jvmargs=-Xmx8192m -XX:+PreserveFramePointer > This property is not honoured by NetBeans when it starts a Gradle daemon, so > I end up with a Gradle daemon using the "default" amount of RAM, which on > some machines is too little, and on some is too much (it's 25% of system RAM). > I'm guessing this is because it's loaded by the wrapper, not the daemon, > because other properties like org.gradle.daemon.idletimeout=36 are > honoured by NB's gradle daemon. > The other effect of not loading that property is that I get multiple gradle > dameons running, each consuming 16Gb of RAM, because they're "incompatible", > so fixing this will save me about 16Gb of RAM per system. > I'm a bit shaky on this bug report, but ... I think this is what's going on. > (footnote: oh dear, Shevek broke something again, what on earth is that idiot > doing with NetBeans and why can't Shevek just behave like a "normal" > developer :D :D) -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
