Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression 4.0.1 -> 4.0.2 #71

Closed
simlu opened this issue Nov 11, 2018 · 5 comments
Closed

Regression 4.0.1 -> 4.0.2 #71

simlu opened this issue Nov 11, 2018 · 5 comments

Comments

@simlu
Copy link
Contributor

simlu commented Nov 11, 2018

After updating from 4.0.1 to 4.0.2 I get an error:

/var/lang/bin/node: symbol lookup error: /user/project/node_modules/lzma-native/binding-v4.0.2-node-v57-linux-x64/lzma_native.node: undefined symbol: _ZN2v87Isolate19CheckMemoryPressureEv

Any idea what's going on here?

Thank you very much! L~

@addaleax
Copy link
Owner

@simlu Can you share more information? In particular, which version of Node.js are you using?

@simlu
Copy link
Contributor Author

simlu commented Nov 13, 2018

If you're looking for a way to easily reproduce, we are running docker image lambci/lambda:build-nodejs8.10.

Let me know if desired and I can produce a more complete example!

@addaleax
Copy link
Owner

addaleax commented Nov 13, 2018

Thanks, I figured out what the issue is: nodejs/node#21269 (comment)

It’s a bit unfortunate… I can do a new lzma-native release tomorrow, but in the meantime you may want to consider upgrading Node.js to v8.12.0+ if you can? That might be desirable anyway, there have been 2 security releases since Node 8.10. 😕 (Edit: Just figured out that this is bound to the versions AWS Lambda uses. I guess this is not an option then…)

(And otherwise, as a temporary workaround, using npm install --build-from-source works if you have a compiler toolchain installed.)

@simlu
Copy link
Contributor Author

simlu commented Nov 13, 2018

@addaleax Thank you for the quick investigation!

Yeah, unfortunately we will be stuck on 8.10 for a while. AWS doesn't update lambda versions very often. We're ok with waiting for the next lzma-native release though.

Thanks again very much for your help! L~

addaleax added a commit that referenced this issue Nov 14, 2018
@addaleax
Copy link
Owner

Okay, just released v4.0.3 – let me know if you run into any trouble :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants