-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Java OutOfMemoryError with some Sequence diagrams #348
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
Comments
I found the problem. It is E.g. in your case with the Without teoz (or in our case an additional If you don't need the overall boundary then you can simply fix it with an @startuml
!include https://raw.githubusercontent.com/plantuml-stdlib/C4-PlantUML/master/C4_Sequence.puml
'following fixes your memory problem
!pragma teoz false Best regards PS.: I entered an issue in forum, but I'm not sure if we can get a fix |
Hi @SlavaVedernikov, a second alternative could be that you increase the available memory, e.g. start the tool with 8GB like java -Xms8192m -Xmx8192m -jar plantuml.jar "YOUR_FILE.puml" but then the build is very slow (I checked it on my machine and the C4-Stdlib version requires ~1min40sec instead of ~5sec if you build it without teoz) BR |
Hi @kirchsth Thank you for investigating this. Thanks, |
Not sure yet, but we might might want to add "does not always play well with teoz" to the docs "somewhere". |
The root cause of this issue has been identified: plantuml/plantuml#1777 (comment) We will commit the fix in the incoming days. |
Hi all, FYI: This is now fixed on PlantUML V1.2024.5.
Regards. |
I'm generating C4-PlantUML diagrams as output from my own framework, and it works great in general. thank you.
I'm having issues with some Sequence diagrams though. Java throws an OutOfMemoryError.
Here is an example of the Sequence diagram that does not render.
...and here is the same diagram written just in PlantUML, which renders successfully.
Please let me know if I'm doing something unexpected/wrong etc. ...or maybe it's a bug (?)
The text was updated successfully, but these errors were encountered: