Beck

np mate, viva la open source :D

 Here is another interesting results. It seems something gc is cleaning after all, but not all.

I'll try to find the most leaking variables. Have you found anything? You can go through your code, you know it better, for me better to analyze from outside. :)

 Here is the info of the heap, sorted by retained size. There are multiple window instances as i understand, one for each parsed page. And they are linked somewhere...

Each is eating about 20mb~ of memory and holds all inner instances like dom elements etc.

78*20=1560 (1392mb~)

Seems like closing/disconnecting client gracefully before closing the server helped in my case, but this is still a bug, not sure why Error is counted as unhandled. Don't have time...

Bump, indeed, it's strange that this is not implemented. It's very important as well for us. Why this wasn't implemented?

There is official swagger node module, which does exactly that, but we choose this module, because it's updated more often. Maybe you can look how that is implemented in their...

https://github.com/swagger-api/swagger-node