Closed
Description
Problem description
Node 14 has some breaking changes regarding ArrayBuffers as noted here nodejs/node#30782 and https://nodejs.org/en/blog/release/v14.0.0/
Multiple ArrayBuffers pointing to the same base address are no longer allowed by V8. This may impact native addons.
Reproduction steps
I don't have solid/standalone reproduction steps as of yet, but there is a relevant issue here with the same stacktrace that we received: pulumi/pulumi#4258 (comment)
Environment
- OS name, version and architecture: Ubuntu 19.10
- Node version: 14.0.0
- Node installation method: nvm
- If applicable, compiler version:
- Package name and version: gRPC@1.24.2
Activity
murgatroid99 commentedon May 6, 2020
Thank you for the information. I will try to fix this; any additional information will help.
I suggest switching to
@grpc/grpc-js
. We will be concentrating most of our development efforts on that library going forward.strigona-worksight commentedon May 6, 2020
Thanks for your reply! We'll look into switching over to the grpc-js.
strigona-worksight commentedon Jun 9, 2020
We had to hold off on switching to grpc-js as the healthcheck is still using the native grpc.
We tried out grpc 1.24.3 with node v14.4.0 and haven't had any issues yet. The release says Node 14 support was added, though I couldn't find any commits tied to that claim. Not sure if this is safe to close or not.
hugebdu commentedon Sep 6, 2020
Same here
cannot switch to
@grpc/grpc-js
due to missing deadlines/cancellations support:(
strigona-worksight commentedon Sep 8, 2020
@hugebdu What version of grpc and node are you using? We haven't had any crashes with the latest versions.
hugebdu commentedon Sep 9, 2020
@strigona-worksight
grpc: 1.24.3
node: 14.9.0
happens only in gRPC server. client is fine.
hugebdu commentedon Oct 27, 2020
minimal reproduction code I've managed to distill.
related to
grpc.Metadata
https://github.com/hugebdu/node14-grpc-core-crashes
murgatroid99 commentedon Oct 27, 2020
OK, knowing that the bug triggers from receiving metadata narrowed it down enough. I think the issue is with the use of this function. I think I can publish a patch soon to fix that.
hugebdu commentedon Oct 27, 2020
that would be awesome!
unfortunately we cannot switch to js implementation and obviously want to upgrade to node 14 once LTS.
thanks a lot
murgatroid99 commentedon Nov 12, 2020
I have published version 1.24.4 with a change to address this bug. Please try that out and tell us if you still have these problems.
hugebdu commentedon Nov 16, 2020
@murgatroid99
works like a charm!
confirmed.
thanks a lot.
murgatroid99 commentedon Nov 16, 2020
OK, I'm going to consider this fixed and close the issue. If anyone experiences this kind of error with version 1.24.4 or later, please comment and I will reopen the issue.
3 remaining items