nginx reload - effectively memory leak

When running nginx -s reload, nginx is meant to soft reload (gradually close existing connections on the Old process, and service new requests on the New process). It does that, except it seems that (perhaps) an active request isn't completing on the old process. Producing a runaway condition whereby if multiple reloads are attempted, the server will eventually run out of ram. Is there a way (c++ module maybe?) to dump what connections nginx is servicing on a **specific** linux pid? I'm unsure how I can solve this, unless I can find out precisely what isn't allowing nginx to shut itself down. *(and I can't just turn sites off to divide/conquer, it's a live client server with 200+ websites)* nginx version: nginx/1.24.0