seregamorph commented on PR #1938: URL: https://github.com/apache/maven-resolver/pull/1938#issuecomment-4825792678
After rerunning the build I have OOM problems. The implementation consumes memory quite actively (for 3.9.16 it's enough to have only 9g): <img width="560" height="406" alt="Screenshot 2026-06-28 at 12 20 26" src="https://github.com/user-attachments/assets/512da0a2-0260-4747-a909-4f58c44d2f28"; /> At some points the process gets stuck, the stack trace is: ``` "mvn-turbo-builder-data-migration-between-regions-temporal-organizations-integration-test" #45 prio=5 os_prio=31 cpu=66339.06ms elapsed=229.64s tid=0x000000099b6cd800 nid=0xda03 runnable [0x00000001734f5000] java.lang.Thread.State: RUNNABLE at org.eclipse.aether.util.graph.transformer.PathConflictResolver$Path.addChildren(PathConflictResolver.java:680) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$Path.access$2200(PathConflictResolver.java:386) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:350) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.gatherCRNodes(PathConflictResolver.java:352) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.build(PathConflictResolver.java:339) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.<init>(PathConflictResolver.java:328) at org.eclipse.aether.util.graph.transformer.PathConflictResolver$State.<init>(PathConflictResolver.java:253) at org.eclipse.aether.util.graph.transformer.PathConflictResolver.transformGraph(PathConflictResolver.java:168) at org.eclipse.aether.util.graph.transformer.ConflictResolver.transformGraph(ConflictResolver.java:290) at org.eclipse.aether.util.graph.transformer.ChainedDependencyGraphTransformer.transformGraph(ChainedDependencyGraphTransformer.java:72) at org.eclipse.aether.internal.impl.collect.DependencyCollectorDelegate.collectDependencies(DependencyCollectorDelegate.java:284) at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:79) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:247) at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:154) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:231) at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:140) ``` Regarding the stuck state - I've already seen this, it happens once in a while. But this actually means there is a wrong multi-thread implementation somewhere and at scale these problems will happen quite often. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
