OpenAPITools / OpenAPITools/openapi-generator

[BUG] OutOfMemeoryError: Java heap space - Potential memory leak?

Open
#23,849 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue: Bug
Dominant language
Java
Stars
26.8k
Forks
7.7k
PR merge metrics
PR metrics pending

Description

Bug Report Checklist
  • [ x] Have you provided a full/minimal spec to reproduce the issue?
  • Have you validated the input using an OpenAPI validator?
  • 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 downloading the binary and running it against a specific yaml and error is thrown:

Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
	at com.fasterxml.jackson.core.util.TextBuffer.carr(TextBuffer.java:1235)
	at com.fasterxml.jackson.core.util.TextBuffer.expand(TextBuffer.java:1191)
	at com.fasterxml.jackson.core.util.TextBuffer.append(TextBuffer.java:861)
	at com.fasterxml.jackson.core.io.SegmentedStringWriter.write(SegmentedStringWriter.java:78)
        at ...

I have tried increasing the maximum memory allocation by using -Xmx=24g. I don't think that there should be any reason to require any more than that. I assume there is a potential memory-leak

openapi-generator version
❯ java -jar openapi-generator-cli.jar version
7.22.0
OpenAPI declaration file content or url

Tripletex API: https://tripletex.no/v2/openapi.json

Generation Details

Attached is the log of the execution run. No other config is changed.

log.txt

Steps to reproduce
  1. Installed the binary directly using the wget ... command as provided in the readme.
  2. Executed the following:
java -jar -Xmx24G openapi-generator-cli.jar generate -i https://tripletex.no/v2/openapi.json -g python -o .

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the documented Java command with openapi-generator-cli 7.22.0 against the Tripletex OpenAPI URL and review log.txt alongside the OutOfMemoryError stack trace. Trace whether the failure is specific to Python generation or the input document. Done means the cause is isolated and generation completes within reasonable memory, or the issue is reduced to a reproducible generator defect with a focused failing case.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, openapi, python
Domain
backend-api-design, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.