Large XML responses in try-now cause Chrome to become unresponsive

[colvinco]

I was testing with the Swagger Pet Store example spec which has this findByStatus method, which when queried with status=available returns ~147 KB of XML. https://petstore.swagger.io/v2/pet/findByStatus?status=available

Calling that from the example in Chrome [Version 102.0.5005.63 (Official Build) (64-bit)] hangs the page.

Repro steps:

1. Go to https://rapidocweb.com/examples/example1.html#get-/pet/findByStatus
2. Select application/xml as the response type in the Response Example section
3. Set status to available
4. Click try...
5. In Chrome, the response isn't formatted and if you click on it the page just hangs
6. If you instead set status=not-a-status then you get a smaller XML response because there's no matches and chrome handles that okay.