-
Notifications
You must be signed in to change notification settings - Fork 411
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
Out of memory errors after migrating to Dokka v2.0.0-Beta #3955
Comments
Hello! We are aware of high memory consumption in the Dokka engine, but so far the only way to address it is increasing heap size for Gradle workers. This patch applied to the dokka-convention plugin helped me to build documentation for aws-sdk-kotlin (for all bootstrapped services as well)
|
Hi, I've tried to reproduce the problem but I get an error about a missing plugin
|
@atyrin Thanks for the suggestion. I saw this in the migration guide and it didn't work for me at one point. Trying it again, and on the latest release Dokka 2.0.0, it's working great. Thanks for your help! @adam-enko I haven't seen this issue before... that's not a plugin we publish or depend on. 🤔 If you're still curious to reproduce the issue, I recommend bootstrapping a single service to start (pick your favorite one) and making sure it can build. If it still fails, let me know. There shouldn't be any plugins declared in that location: |
Describe the bug
We are running into
java.lang.OutOfMemoryError: Java heap space
after migrating to Dokka 2.0.0-Beta, but only when building docs for our AWS SDK service clients. We have no trouble generating docs for our runtime projects.Expected behaviour
Dokka should not run out of memory.
Screenshots
N/A
To Reproduce
Dokka configuration
We use a fairly simple configuration, but it's spread across many projects. Check the root project's
build.gradle.kts
, the services project'sbuild.gradle.kts
, and the newly-created Dokka conventions plugin for the relevant config.I've also tried the two tips provided in the troubleshooting section of the migration guide, which didn't work.
Installation
Additional context
Add any other context about the problem here
The text was updated successfully, but these errors were encountered: