Andrew Tatomyr

@roman-sainchuk please take a look.

Hi @ldanielw1, what command are you trying to run? What are the arguments? What is the file type, what's the spec version? Any logs output?

It's hard to figure out what's wrong without a reproducible sample. The tool does not use any CPU-intensive dependencies. But during the execution of the `build-docs` command react content is...

Interesting. It still creates the `components` section for a `--dereferenced` bundle. So it should be possible to reference those schemas directly. I slightly modified the example: **openapi.yaml**: ```yaml openapi: 3.1.0...

@its-hammer-time no idea TBH. It's currently under review, and I'll release it as soon as it gets merged. However, I cannot predict when (or even whether) it will be approved.

The fix is available in `v1.25.8`. @its-hammer-time, please let me know if it works for you.

Hi @its-hammer-time! Could you check whether it also hangs outside the docker container (when installed globally with `npm install -g @redocly/cli` and run via `redocly bundle --remove-unused-components --dereferenced openapi.yaml -o...

I don't think the issue you've mentioned is related to your case. The memory issue crops up with the build-docs command (which runs the React renderer) while you're using bundle....

Thank you! I'll review the example a bit later.

Hi @its-hammer-time, I've examined all the changes between those versions and haven't found anything suspicious that could potentially cause the issue. I'm going to close this issue as it's not...