Nasty client memory leak

[rorph]

I've been using ws client on server-side to do multiplexing, turns out it has a nasty memory leak on upgradeHeader handler.

The server was patched, but looks like the client wasn't.
I'm attaching a patch file with the fix for this.

WebSocket.patch

Cheers

[Eeems]

You may want to open a pull request instead of attaching a patch file.

[rupamkhaitan]

Is this patch for memory leak on the server side?
We use ws library to open socket connection on our server side, will this patch have impact on memory leak on server side?

[JoshuaWise]

If anyone is still experiencing this, please reopen the issue of submit a pull request.