Segmentation fault on w. @google-cloud/bigtable@6.2.0

[radn-dr]

I get a segmentation fault error when running a node app with @google-cloud/bigtable@6.2.0 import.

There is no issue when using version 6.1.0.

The error occurs when simply importing the library into a file and running it.

• OS: macOS Sequoia Version 15.5 (24F74)
• Node.js version: v18.16.0
• npm version: 9.6.6
• @google-cloud/bigtable version: 6.2.0

Steps to reproduce

1. npm install @google-cloud/bigtable
2. const { Bigtable } = require("@google-cloud/bigtable");

[danieljbruce]

I can't reproduce the issue. If you continue to see the error then please reopen and post the script you are trying to run.

[jlogsdon]

Same issue here. Looks like its an issue with fast-crc32c on apple silicon.

[pkriete]

@danieljbruce We can consistently reproduce on apple silicon, can we get this reopened?

[BenAychh]

We had to downgrade to 6.1.0 because our devs were unable run anything locally on our Macs.

[jiaxin-lin]

Same here on all our devs machines

[omer-optimi]

Why this issue was closed? The problem still happens on my apple silicon M3 computer (starting from version 6.2.0).
Script? any code that import this library (no need to write anything special, just import the package)

[danieljbruce]

Can you try following the steps from https://gist.github.com/adrienjoly/e29a6e73fb7e701eefd80ff9bde9abeb posted in the related bug? This may resolve the issue.

[jlogsdon]

Start a new shell using Rosetta2

Requiring us to use Rosetta is not an acceptable fix.

[jlogsdon]

As another data point here, I spun up an ARM VM in GCP (C4A).

bigtable-arm-test:~# node
Welcome to Node.js v18.20.4.
Type ".help" for more information.
> require('@google-cloud/bigtable')
node: symbol lookup error: /root/node_modules/sse4_crc32/build/Release/crc32c.node: undefined symbol: _Z18sse42_is_availablev
bigtable-arm-test:~# arch
aarch64

So if we wanted to run ARM servers we would be stuck on 6.1.0 as well, even if Rosetta was an acceptable work around for the Apple Silicon side.

[feywind]

I was able to repro this on my M1 Mac, so we're looking at workarounds now. It looks like this was introduced with the Execute Query feature:

#1613

I'm guessing that the segfault happens when the module loads and tries various backends, but that's as far as I've gotten so far.

Edit: re trying various backends