Segmentation fault (core dumped)

[Rinse12]

Define You:

Hey, saw the project on Bluesky and I love the idea. We're working on a p2p social media and are curious about new projects in the p2p ecosystem. I tried to run your app image but got this error:

(node:2310725) ExperimentalWarning: Import assertions are not a stable feature of the JavaScript language. Avoid relying on their current behavior and syntax as those might change in a future version of Node.js.
(Use `peersky-browser --trace-warnings ...` to show where the warning was created)
(node:2310725) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
No existing ENS cache file found. Starting with an empty cache.
Initializing IPFS node...
Loaded libp2p key from<redacted>
Peer ID: <redacted>
Node userAgent: peersky-browser/1.0.0-beta.15 js-libp2p/2.10.0 electron/29.4.6
IPFS node initialized in 1134ms
Patched node peerId to include toBytes() method.
Patched node peerId to include bytes property.
Initializing Hyper SDK...
Generated new swarm keypair
Segmentation fault (core dumped)

[akhileshthite]

Thanks for opening the issue!

What OS, Linux distro/version, CPU architecture, and kernel are you running the AppImage on?

In our upcoming release we’re upgrading to the latest Electron version #81

[Rinse12]

I'm on kernel 6.8.0, ubuntu 22, x86_64

[Ayush-Vish]

@akhileshthite Confirming the same happens in my OS as well.

{18:21}~ ➭ cat /etc/os-release 
NAME="Linux Mint"
VERSION="22 (Wilma)"
ID=linuxmint
ID_LIKE="ubuntu debian"
PRETTY_NAME="Linux Mint 22"
VERSION_ID="22"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=wilma
UBUNTU_CODENAME=noble

[Asherathe]

peersky-browser-1.0.0-beta.17-linux-x86_64.AppImage still segfaults right after generating new swarm keypair on up-to-date openSUSE Tumbleweed using kernel 6.18.9-1.1.

(node:167026) ExperimentalWarning: Import assertions are not a stable feature of the JavaScript language. Avoid relying on their current behavior and syntax as those might change in a future version of Node.js.
(Use `peersky-browser --trace-warnings ...` to show where the warning was created)
(node:167026) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
No existing ENS cache file found. Starting with an empty cache.
Initializing IPFS node...
Loaded libp2p key from /home/user/.config/peersky-browser/ipfs/libp2p-key
Peer ID: 12D3KooWDhC1qwEqXXXgXerdLecTnm7M9rbW3zfo5XRy9dZB12Us
Node userAgent: peersky-browser/1.0.0-beta.17 js-libp2p/2.10.0 electron/29.4.6
IPFS node initialized in 1439ms
Patched node peerId to include toBytes() method.
Patched node peerId to include bytes property.
Initializing Hyper SDK...
Generated new swarm keypair
Segmentation fault         (core dumped) ./peersky-browser-1.0.0-beta.17-linux-x86_64.AppImage

[akhileshthite]

@Asherathe Hey, working on #81 now (#107 (comment)).
I don't have linux machine rn. Could you switch to the web-extensions branch, run npm run build-all, and test the linux-x86_64.AppImage build?

[Asherathe]

@Asherathe Hey, working on #81 now (#107 (comment)). I don't have linux machine rn. Could you switch to the web-extensions branch, run npm run build-all, and test the linux-x86_64.AppImage build?

Looks like it still segfaults in the same place with the updated Electron.

No existing ENS cache file found. Starting with an empty cache.
[Session] Using defaultSession (feature flag disabled)
Initializing IPFS node...
Loaded libp2p key from /home/user/.config/peersky-browser/ipfs/libp2p-key
Peer ID: 12D3KooWDhC1qwEqXXXgXerdLecTnm7M9rbW3zfo5XRy9dZB12Us
Node userAgent: peersky-browser/1.0.0-beta.17 js-libp2p/2.10.0 electron/37.10.3
IPFS node initialized in 1054ms
Patched node peerId to include toBytes() method.
Patched node peerId to include bytes property.
Initializing Hyper SDK...
Generated new swarm keypair
Segmentation fault         (core dumped) ./peersky-browser-1.0.0-beta.17-linux-x86_64.AppImage

[akhileshthite]

@Asherathe Hey, working on #81 now (#107 (comment)). I don't have linux machine rn. Could you switch to the web-extensions branch, run npm run build-all, and test the linux-x86_64.AppImage build?

Looks like it still segfaults in the same place with the updated Electron.

No existing ENS cache file found. Starting with an empty cache.
[Session] Using defaultSession (feature flag disabled)
Initializing IPFS node...
Loaded libp2p key from /home/user/.config/peersky-browser/ipfs/libp2p-key
Peer ID: 12D3KooWDhC1qwEqXXXgXerdLecTnm7M9rbW3zfo5XRy9dZB12Us
Node userAgent: peersky-browser/1.0.0-beta.17 js-libp2p/2.10.0 electron/37.10.3
IPFS node initialized in 1054ms
Patched node peerId to include toBytes() method.
Patched node peerId to include bytes property.
Initializing Hyper SDK...
Generated new swarm keypair
Segmentation fault         (core dumped) ./peersky-browser-1.0.0-beta.17-linux-x86_64.AppImage

Thanks for checking, will look into it!
I just realized I do have a Pi 5

[akhileshthite]

@Rinse12 @Asherathe @Ayush-Vish

I've fixed the issue in this PR: #119

Please test it and let me know. You can download and install the builds from here:
https://github.com/p2plabsxyz/peersky-test/releases/tag/v1.0.0-beta.0

[Asherathe]

@Rinse12 @Asherathe @Ayush-Vish

I've fixed the issue in this PR: #119

Please test it and let me know. You can download and install the builds from here: https://github.com/p2plabsxyz/peersky-test/releases/tag/v1.0.0-beta.0

Unfortunately, I'm still seeing the issue with the test build.

No existing ENS cache file found. Starting with an empty cache.
[Session] Using defaultSession (feature flag disabled)
Initializing IPFS node...
No libp2p key found at /home/user/.config/peersky-test/ipfs/libp2p-key, will generate a new one
Saved libp2p key to /home/user/.config/peersky-test/ipfs/libp2p-key
Peer ID: 12D3KooWLvwxMbgzTZgoXckk9e2rUeDtfzXDb9U1MMoU6JHxuF25
Node userAgent: peersky-browser/1.0.0-beta.0 js-libp2p/3.1.3 electron/37.10.3
IPFS node initialized in 1257ms
Initializing Hyper SDK...
Generated new swarm keypair
Segmentation fault         (core dumped) ./peersky-test-1.0.0-beta.0-linux-x86_64.AppImage

[akhileshthite]

@Rinse12 @Asherathe @Ayush-Vish
I've fixed the issue in this PR: #119
Please test it and let me know. You can download and install the builds from here: https://github.com/p2plabsxyz/peersky-test/releases/tag/v1.0.0-beta.0

Unfortunately, I'm still seeing the issue with the test build.

No existing ENS cache file found. Starting with an empty cache.
[Session] Using defaultSession (feature flag disabled)
Initializing IPFS node...
No libp2p key found at /home/user/.config/peersky-test/ipfs/libp2p-key, will generate a new one
Saved libp2p key to /home/user/.config/peersky-test/ipfs/libp2p-key
Peer ID: 12D3KooWLvwxMbgzTZgoXckk9e2rUeDtfzXDb9U1MMoU6JHxuF25
Node userAgent: peersky-browser/1.0.0-beta.0 js-libp2p/3.1.3 electron/37.10.3
IPFS node initialized in 1257ms
Initializing Hyper SDK...
Generated new swarm keypair
Segmentation fault         (core dumped) ./peersky-test-1.0.0-beta.0-linux-x86_64.AppImage

Hmm, I guess previous fix in the PR didn’t resolve the Linux segfault because it relied on asar: false and didn’t reliably exclude/unwrap the native sodium-native binaries Electron loads during hypercore-crypto.keyPair(), so now I'll try to ship with npmRebuild: true plus asar: true + asarUnpack (and exclude nested sodium-native) to make sure the correct Electron-native binaries are packaged and loaded on Linux.

Will let you know once I release it.

[akhileshthite]

Alright, I found the fix:
hypercore-protocol is never imported or used in hyper-sdk; it's a leftover from before hypercore@11.x internalized the protocol layer. I've identified and removed this single dependency from hyper-sdk's package.json RangerMauve/hyper-sdk#105.

Once that's published, we'll update our dependencies and the segfault should be resolved without needing build config workarounds.

[akhileshthite]

Alright, I found the fix: hypercore-protocol is never imported or used in hyper-sdk; it's a leftover from before hypercore@11.x internalized the protocol layer. I've identified and removed this single dependency from hyper-sdk's package.json RangerMauve/hyper-sdk#105.

Once that's published, we'll update our dependencies and the segfault should be resolved without needing build config workarounds.

Released new version of hyper-sdk, download the latest builds and let me know if you're still facing any issues: https://github.com/p2plabsxyz/peersky-test/releases/tag/v1.0.0-beta.0