You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Platform: Linux NREXPRESS 3.10.0-693.el7.x86_64 deps: update openssl to 1.0.1j #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux (Cent OS 7.4)
Subsystem: zlib
What steps will reproduce the bug?
Unfortunately this bug is triggered very rarely on a production system, so I haven't been able to write short code to reproduce the issue. This has been reported earlier also in node 6.x and it was mentioned that this was caused by websocket closed in middle of things.
How often does it reproduce? Is there a required condition?
This is very rare. There is no exact condition to reproduce this issue but it occurs typically when production system is very busy.
What is the expected behavior?
If websocket has been closed in middle of writing something, process should not throw exception.
What do you see instead?
TypeError: Cannot read property 'write' of null at Zlib.callback (zlib.js:499:33)
Additional information
This issue has been reported earlier on node 6.X and it has been mentioned that it is resolved in node 8.x but looks like it is not resolved. just wanted to check what version this issue has been resolved if we upgrade node.
The text was updated successfully, but these errors were encountered:
Node.js versions 6.x and 8.x are unfortunately no longer supported. I suggest you try to upgrade to a more recent version (v14.x or v12.x would be preferable, as v10.x is going to reach end of life in less than 6 months) and reopen an issue if you still experience this.
#15625
What steps will reproduce the bug?
Unfortunately this bug is triggered very rarely on a production system, so I haven't been able to write short code to reproduce the issue. This has been reported earlier also in node 6.x and it was mentioned that this was caused by websocket closed in middle of things.
How often does it reproduce? Is there a required condition?
This is very rare. There is no exact condition to reproduce this issue but it occurs typically when production system is very busy.
What is the expected behavior?
If websocket has been closed in middle of writing something, process should not throw exception.
What do you see instead?
TypeError: Cannot read property 'write' of null at Zlib.callback (zlib.js:499:33)
Additional information
This issue has been reported earlier on node 6.X and it has been mentioned that it is resolved in node 8.x but looks like it is not resolved. just wanted to check what version this issue has been resolved if we upgrade node.
The text was updated successfully, but these errors were encountered: