node_http2.cc: void node::http2::Http2Session::CheckAllocatedSize(size_t) const: Assertion `(current_nghttp2_memory_) >= (previous_size)' failed.

[huan]

When upgrading from grpc to grpc-js, we encountered the following error in tests/integration.spec.ts:

grpc/tests/integration.spec.ts

Lines 91 to 93 in 920bebd

	eventStream.cancel()
	await new Promise<void>(resolve => server.tryShutdown(resolve))

node[122920]: ../src/node_http2.cc:449:void node::http2::Http2Session::CheckAllocatedSize(size_t) const: Assertion `(current_nghttp2_memory_) >= (previous_size)' failed.

Node Versions

All node major versions will be affected: 10/12/14/15

Similiar Issues

• Grpc js ExchangeUnion/xud#1605 (comment)
• GRPC assertion failure when subscribing to streams EventStore/EventStore-Client-NodeJS#125
• @grpc/grpc-js Abort on ClientReadableStream cancel grpc/grpc-node#1652
• @grpc/grpc-js: Closing Stream After Unary Call Triggers Double Free grpc/grpc-node#1464

Workaround

+ await new Promise(resolve => setImmediate(resolve))
eventStream.cancel() 

[mdouglass]

I opened nodejs/node#38964 against nodejs as I ran into the same assertion failure you saw. The same setImmediate fix you suggested helps with my repro case as well, but thought you might want to track the issue on nodejs side as well.

[huan]

Thanks for filing the issue on the nodejs side, I believe there must be a bug in nodejs and it should be definitely fixed.

[huan]

According to nodejs/node#38964 (comment) I believe this problem will be fixed in the next major version of Node.js.

However, for maximum compatibility for our module, we should keep this workaround "as-it-is", which means we will not remove the workaround.