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

Memory regression when resolving large artifacts while computing checksums #11966

Closed
melix opened this issue Jan 22, 2020 · 0 comments · Fixed by #11969
Closed

Memory regression when resolving large artifacts while computing checksums #11966

melix opened this issue Jan 22, 2020 · 0 comments · Fixed by #11969
Assignees
Milestone

Comments

@melix
Copy link
Contributor

@melix melix commented Jan 22, 2020

Current behavior

The org.gradle.internal.hash.ChecksumHasher#hash(File) method loads whole files in memory, it doesn't have to.

This can cause out of memory issues during publication when hashing large artifacts (several hundreds of MBs).

@melix melix added this to the 6.2 RC1 milestone Jan 22, 2020
@melix melix self-assigned this Jan 22, 2020
@melix melix added the in:dependency-management label Jan 22, 2020
@big-guy big-guy removed this from the 6.2 RC1 milestone Jan 24, 2020
@big-guy big-guy added this to the 6.1.1 milestone Jan 24, 2020
@big-guy big-guy changed the title Don't load the whole file in memory when computing checksums Memory regression when resolving large artifacts while computing checksums Jan 24, 2020
ausatiy added a commit to JetBrains/kotlin that referenced this issue Mar 11, 2021
ausatiy added a commit to JetBrains/kotlin that referenced this issue Mar 15, 2021
Gradle 6.1 is not suitable for testing because of memory leak on
artefact validation (gradle/gradle#11966)
ausatiy added a commit to JetBrains/kotlin that referenced this issue Mar 15, 2021
Gradle 6.1 is not suitable for testing because of memory leak on
artefact validation (gradle/gradle#11966)

(cherry picked from commit 9c00000)
ausatiy added a commit to JetBrains/kotlin that referenced this issue Mar 15, 2021
Gradle 6.1 is not suitable for testing because of memory leak on
artefact validation (gradle/gradle#11966)

(cherry picked from commit 9c00000)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants