[
https://issues.apache.org/jira/browse/NETBEANS-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023950#comment-17023950
]
Shevek commented on NETBEANS-3744:
----------------------------------
I added `-J-Dorg.netbeans.modules.gradle.GradleProjectCache.level=ALL` and the
effect was that NetBeans didn't load the projects in any meaningful sense at
all. It just became a dumb text editor. I saw something about
JavacParserFactory returned null parser for <file.java>. I tried two reloads of
NetBeans - both of which were really fast, but useless. Removing the flag again
now....
wait, hang on, it's broken even without the flag. ARGH... ARRRRRRRRRGH!!!!!!!
so, wait, tools, plugins, intall nb-javac... but it was INSTALLED 5 minutes
ago, I was USING it... Also the race conditions refactoring across modules are
killing me today.##
Reenabling Gradle logging again for next restart. ....
no, as far as I can tell, now, NB isn't invoking or talking to Gradle at all,
and so isn't seeing my classpath updates, so now it can't build my code.
> NetBeans should load multi-project gradle projects in one shot
> --------------------------------------------------------------
>
> Key: NETBEANS-3744
> URL: https://issues.apache.org/jira/browse/NETBEANS-3744
> Project: NetBeans
> Issue Type: Bug
> Affects Versions: 11.1, 11.2
> Environment: Gradle 5.6 definitely exhibits this. Haven't tried 6.x
> yet.
> I think Gradle 4.10.3 did not have the issue, but we didn't have 100
> subprojects and/or use a shared build cache back then either.
> Reporter: Shevek
> Priority: Major
> Attachments: netbeans-gradle-out-of-memory.png
>
>
> It appears that NB does a gradle "build" (model, whatever) per subproject in
> a multi module project. Given a project with say 100 subprojects, two things
> happen:
> 1. It takes FOREVER, because 100 invocations of gradle takes FOREVER.
> 2. It never completes, because after 30 or 40 projects, Gradle runs out of
> RAM, and the Gradle JVM goes into GC Ergonomics while holding various
> system-wide Gradle locks, and now the entire system is hung and NO Gradle
> invocation on that system can proceed.
> Please can NetBeans load this project-set in one bite, with a single
> invocation, from which it can get all the model data (like it used to with
> the old Gradle plugin)?
> This is the major reason why NetBeans takes such a long time to load, and
> frequently, when it detects file changes, I can only get NB to be usable
> again by restarting it.
> I already gave Gradle 10Gb of RAM; the project is definitely buildable and
> testable in 2Gb, the rest is caches/leaks/whatever, that's Gradle's proble
> but it's vastly exacerbated by the NB Gradle model-loading strategy.
> Related: NETBEANS-3041 which at least gives me the 10Gb. Before that, I think
> NB just used to crash.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
