OpenAPITools / OpenAPITools/openapi-generator
[BUG][JAVA] OutOfMemoryError Required array length 2147483638 + 2317306 is too large
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Bug Report Checklist
- Have you provided a full/minimal spec to reproduce the issue?
- Have you validated the input using an OpenAPI validator (example)?
- Have you tested with the latest master to confirm the issue still exists?
- Have you searched for related issues/PRs?
- What's the actual output vs expected output?
- [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description
When building a csharp api client with this command generates the error when building the client
npm exec @openapitools/openapi-generator-cli generate -- -g csharp --skip-operation-example -i "swagger.json" -o "/openapi/csharp"
Building clients for Java, Python, and PHP all work without issue.
I would expect the same for csharp
openapi-generator version
10.8.2
OpenAPI declaration file content or url
the swagger file is over 14MB and has 479491 lines. It's generated from source code using Swashbuckle
Generation Details
export JAVA_TOOL_OPTIONS="-Xmx30g"
export DOTNET_SYSTEM_RUNTIME_GCALLOWVERYLARGEOBJECTS=true
npm install @openapitools/openapi-generator-cli -g
npm exec @openapitools/openapi-generator-cli generate -- -g csharp --skip-operation-example -i "swagger.json" -o "/openapi/csharp"
Related issues/PRs
There are a lot of heap issues. I've increased java to 30GB but to no avail. Other client types are build just fine.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the npm exec @openapitools/openapi-generator-cli command with the reported 14MB swagger.json and the csharp generator, then compare it with the Java, Python, or PHP generation that succeeds. Trace where the csharp generation reaches the OutOfMemoryError and verify the fix by completing generation without the array-length failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, java, openapi
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100