-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
[BUG][JAVA] Exception in thread "main" java.lang.OutOfMemoryError: Java heap space #6597
Comments
Any updates on this? |
Hey cobraz, We are experiencing the same issue. I'm going to gather info an post in a few. Thanks, |
@jtrueblood-anaqua Did you get some info to post? |
Bump ❤️ |
Closing this. We have moved away from this library. |
Can we please re-open this? The issue still exists and should be fixed without respect to the original poster using this library or not. |
FYI, one thing I found to get around this was:
|
@agilob @davija reopened. Hope we'll get this fixed :) re |
I will be slowly looking into it step after step, trying to pick low hanging fruits first, one PR is ready #8181 reduces number of open files, closes resources much sooner. Should help, but I didn't do any professional profiling for it. |
I've filed #8731 to workaround the issue for the time being. |
Bug Report Checklist
Description
Trying to generate a quite large ~1mb Swagger-file. It had some validation issues, and I tried to fix them. Don't know if those are relevant, since no matter if it's fixed or not, no dice. Still «Java heap space» issue.
Relevant issue: bjerkio/tripletexjs#14
Reproduce the issue with this repository: https://github.com/bjerkio/tripletexjs/tree/reproduce
openapi-generator version
4.3.1
OpenAPI declaration file content or url
https://raw.githubusercontent.com/bjerkio/tripletexjs/reproduce/swagger-fixed.json
Command line used for generation
make generate
orSteps to reproduce
Related issues/PRs
Suggest a fix
I'm lost.
@bbdouglas @sreeshas @jfiala @lukoyanov @cbornet @jeff9finger @karismann @Zomzog @lwlee2608 @bkabrda
The text was updated successfully, but these errors were encountered: