TLS assertion error in DoWrite

Version: v10.16.3 (we're using nave)
Platform: Linux zagent 4.4.0-159-generic configure: remove workarounds for GCC < 4.8 #187-Ubuntu SMP Thu Aug 1 16:28:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Subsystem: http2

We have this error in high loaded service when customers are making requests to amazon.com (not sure only amazon.com):

/var/lib/nave/installed/10.16.3/bin/node[15992]: ../src/tls_wrap.cc:682:virtual int node::TLSWrap::DoWrite(node::WriteWrap*, uv_buf_t*, size_t, uv_stream_t*): Assertion `(current_write_) == nullptr' failed.
 1: 0x8fa0c0 node::Abort() [/var/lib/nave/installed/10.16.3/bin/node]
 2: 0x8fa195  [/var/lib/nave/installed/10.16.3/bin/node]
 3: 0xa2c90b node::TLSWrap::DoWrite(node::WriteWrap*, uv_buf_t*, unsigned long, uv_stream_s*) [/var/lib/nave/installed/10.16.3/bin/node]
 4: 0xa2a5ec node::TLSWrap::EncOut() [/var/lib/nave/installed/10.16.3/bin/node]
 5: 0xa2b34b node::TLSWrap::OnStreamRead(long, uv_buf_t const&) [/var/lib/nave/installed/10.16.3/bin/node]
 6: 0xa2aad1 node::TLSWrap::ClearOut() [/var/lib/nave/installed/10.16.3/bin/node]
 7: 0xa2b343 node::TLSWrap::OnStreamRead(long, uv_buf_t const&) [/var/lib/nave/installed/10.16.3/bin/node]
 8: 0x9cf801  [/var/lib/nave/installed/10.16.3/bin/node]
 9: 0xa7ae09  [/var/lib/nave/installed/10.16.3/bin/node]
10: 0xa7b430  [/var/lib/nave/installed/10.16.3/bin/node]
11: 0xa80dd8  [/var/lib/nave/installed/10.16.3/bin/node]
12: 0xa6fe6b uv_run [/var/lib/nave/installed/10.16.3/bin/node]
13: 0x904725 node::Start(v8::Isolate*, node::IsolateData*, std::vector<std::string, std::allocator<std::string> > const&, std::vector<std::string, std::allocator<std::string> > const&) [/var/lib/nave/installed/10.16.3/bin/node]
14: 0x90297f node::Start(int, char**) [/var/lib/nave/installed/10.16.3/bin/node]
15: 0x7f9536c18830 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
16: 0x8bbe85  [/var/lib/nave/installed/10.16.3/bin/node]

Can you suggest me what I can do to get you more info about error?
Or maybe you know why this may occur?
We have 1-2 this error per hour for one server.