NSwag uses all available memory when trying to generate the OpenAPI document

[danports]

I just tried adding NSwag to one of my ASP.NET projects running .NET 8 following the docs and when I tried accessing the Swagger UI, it hung on the loading screen. Apparently generating the OpenAPI document on the backend is consuming all available memory on my machine (10GB+ when I got tired of the OS paging everything else out to disk and killed it). Any suggestions on how I can troubleshoot this?

[danports]

It seems like the problem was that the MVC ApiExplorer was pulling in a ton of controller methods, including some with a few dozen parameters, and that was causing memory usage to explode when NSwag tried to enumerate available operations. I'm guessing that ApiExplorer has trouble with methods with many parameters, but in any event, I can work around it with configuration, and it's not an NSwag problem, so I'll close this.