Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java Heap Space exception #17

Open
owenmartin-toast opened this issue Jun 26, 2023 · 2 comments
Open

Java Heap Space exception #17

owenmartin-toast opened this issue Jun 26, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@owenmartin-toast
Copy link

Describe the bug

I am using this plugin via the JFrog CLI, but I receive a Java Heap space exception;

The init script is as follows;

initscript {
    repositories { 
		mavenCentral()
    }
    dependencies {
        classpath 'com.jfrog:gradle-dep-tree:2.2.0'
    }
}

So I am using the latest version.

I have the following in my gradle.properties file in my repository
org.gradle.jvmargs=-Xmx4096M

Current behavior

Exception in thread "Daemon client event forwarder" java.lang.OutOfMemoryError: Java heap space
        at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.addConditionWaiter(AbstractQueuedSynchronizer.java:1896)
        at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2114)
        at java.base/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458)
        at org.gradle.launcher.daemon.server.exec.DaemonConnectionBackedEventConsumer$ForwardEvents.getNextEvent(DaemonConnectionBackedEventConsumer.java:72)
        at org.gradle.launcher.daemon.server.exec.DaemonConnectionBackedEventConsumer$ForwardEvents.run(DaemonConnectionBackedEventConsumer.java:59)

Reproduction steps

No response

Expected behavior

No response

Gradle Dependency Tree version

2.2.0

Operating system type and version

MacOS Ventura

@owenmartin-toast owenmartin-toast added the bug Something isn't working label Jun 26, 2023
@asafgabai
Copy link
Contributor

Hi @owenmartin-toast, the fix for the high memory consumption has been implemented and is now part of version 3.0.0.
Please note that the output structure of the plugin has been changed.
Please let us know if you encounter any further issues or have any additional feedback.

@owenmartin-toast
Copy link
Author

Hi,

I can confirm this fixes the issue, thank you!

Owen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants