We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the major remaining crash is in zlib.js line 623 which is this code:
var newReq = self._handle.write(flushFlag, chunk, inOff, availInBefore, self._buffer, self._offset, self._chunkSize);
self._handle is null:
zlib.js:623 var newReq = self._handle.write(flushFlag, ^ TypeError: Cannot read property 'write' of null at Zlib.callback (zlib.js:623:32)
It is in the process that handles websockets so I suspect the websocket closes in the middle of things. Sounds like a bug in node-core...
The text was updated successfully, but these errors were encountered:
@ggarber @dagingaa thoughts? Who do we know that can debug node shit...
Sorry, something went wrong.
Honestly I would open an issue for it for now, perhaps someone knows outside us?
might be fixed by nodejs/node#5982 / nodejs/node#6034 -- i'll see if I can monkeypatch it on our instance
hrm. This seems to be fixed. Or now it always crashes before running into this.
No branches or pull requests
the major remaining crash is in zlib.js line 623 which is this code:
self._handle is null:
It is in the process that handles websockets so I suspect the websocket closes in the middle of things. Sounds like a bug in node-core...
The text was updated successfully, but these errors were encountered: