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

symbol lookup error: undefined symbol: <from SSL library> (in a native dependency) crashes the electron process #1776

Closed
Delfshkrimm opened this issue Sep 12, 2018 · 1 comment
Labels

Comments

@Delfshkrimm
Copy link

Delfshkrimm commented Sep 12, 2018

Hi everyone,

I'm trying to use the boilerplate with the node module "ursa" (version 0.9.4) which is a native module that needs compilation for my plateform.
For the record, I'm using node 8.11.4 and npm 5.6.0.
So in a vanilla electron-react-boilerplate project, I've included ursa in the ./app/package.json and installed it with npm i in the app/ folder or just run yarn in root folder for it to compile the native module. The compilation works like a charm, no issue here.
Problem is that when I import ursa from 'ursa' in the ./app/index.js and launch the project with yarn dev in root folder, I get the following error in the console, and the electron process crashes

/home/mehdi/Documents/git/proto/node_modules/electron/dist/electron --type=renderer --no-sandbox --service-pipe-token=E7EFA4A047D4F5ACD154E0AA352B6343 --lang=fr --app-path=/home/mehdi/Documents/git/proto/node_modules/electron/dist/resources/default_app.asar --node-integration=true --webview-tag=true --no-sandbox --context-id=2 --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;0,17,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;1,17,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;2,17,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;3,16,3553;3,17,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553;4,16,3553;4,17,3553 --disable-accelerated-video-decode --enable-gpu-async-worker-context --service-request-channel-token=E7EFA4A047D4F5ACD154E0AA352B6343 --renderer-client-id=8 --shared-files=v8_natives_data:100,v8_snapshot_data:101: symbol lookup error: /home/mehdi/Documents/git/proto/app/node_modules/ursa/build/Release/ursaNative.node: undefined symbol: BIO_new_mem_buf

As I read it somewhere, BIO_new_mem_buf seems to be a function from libssl > v0.9 and I have all the requirements installed on my machine (I've tried it with libssl-dev which is v1.1.0f-3+deb9u2 and libssl1.0-dev, doesn't change anything).
On github I've found many related issues to using a native module that fails to link to openssl functions on the local plateform like this fellow here but none of the proposed solutions seem to work for me.

I get the feeling this is related to my plateform and how the links to the ssl libraries are failing when running with the electron process in the boilerplate.
For info, I've also tried running the ursa module in a vanilla electron project (without the boilerplate and webpack) and it works fine...

Any help or just testing on your own plateform would be really appreciated in order to see if this is the default faulty behavior we get using the boilerplate (and help us locate what's going wrong and where)!
Thanks a lot

PS: same issue if I run the project in node 10.10.0 and npm 6.4.1
PPS: I'm using debian 9, a colleague's got the same issue running macOS 10, and another one using also debian 9

@stale
Copy link

stale bot commented Dec 10, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 10, 2018
@stale stale bot closed this as completed Dec 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant