Segmentation fault after compiling #19

git-cd opened this Issue Oct 2, 2013 · 26 comments


None yet

7 participants

git-cd commented Oct 2, 2013

Hey guys, this a great project and I want to help improving it.

After compiling a sample projetct I got the following message when trying to execute the file: Segmentation fault.

Have you already seen that?


@git-cd Hey, I assume this is on Linux, could you post the version and if it is 64-bit or 32-bit?


On Mac/Windows everything works fine. Which node version are you running ?


Im getting the same with ubuntu 12.04 x64, and node v0.10.20

lpetrov commented Oct 3, 2013

I can confirm the same issue here...:

(x)lpetrov@lpetrovvws:/workspace/x/desktop$ ./dist/cache/linux32/0.7.5/nw
Segmentation fault
/workspace/x/desktop$ ./dist/cache/linux64/0.7.5/nw
Segmentation fault
(x)lpetrov@lpetrovvws:/workspace/x/desktop$ uname -a
Linux lpetrovvws 3.5.0-40-generic #62
precise1-Ubuntu SMP Fri Aug 23 17:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
(x)lpetrov@lpetrovvws:~/workspace/x/desktop$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.3 LTS
Release: 12.04
Codename: precise

git-cd commented Oct 3, 2013

@vladikoff Hi, I'm using Ubuntu 13.04 32-bit


Same with ubuntu 12.04 x64, and node v0.10.20


It seems issue in wrong decompressing of the archive from AWS. After manual unpacking tar, build passed successfully =)


I just setup a vagrant box with 12.04.1 LTS x86_64 and did the build - it all ran smooth. Could it be, that the download somehow failed? Can you run the task with --verbose. I'll try to do some better error handling for the download


Hey. Did the app run for you?


Nope only did a short build test - the mac version build on linux worked fine :) Maybe someone how is running linux with a KDE could do some more testing


cd $BULLETIN_CLIENT_BUILD_PATH/cache/linux32/0.7.5/ && tar --strip-components=1 -zxvf node-webkit-v0.7.5-linux-ia32.tar.gz
cd $BULLETIN_CLIENT_BUILD_PATH/cache/linux64/0.7.5/ && tar --strip-components=1 -zxvf node-webkit-v0.7.5-linux-x64.tar.gz
cd $BULLETIN_CLIENT_BUILD_PATH/cache/mac/0.7.5/ && unzip -o
cd $BULLETIN_CLIENT_BUILD_PATH/cache/win/0.7.5/ && unzip -o

After this builded nw is working, I'm can post verbose log here but not now.


ok I got that wrong, it seems like the build works but the un taring does not work. Seems like I have to setup a full linux box after all ...


I can share broken untared files if you need.


hmm did you download them again manually and put em into the cache folder?


I mean already untared files


@LifeBeyondTime Did you download the files again manually or is only the untar broken?


Only untar

This is my cache folder after grunt command, i hope this help you


Now all works fine, I think it's mystic)


I think it's more due to the fact the download doesn't complete, I'll have to look if amazon offers some kind of md5 hashing for the downloads

@steffenmllr steffenmllr added a commit that referenced this issue Oct 8, 2013
@steffenmllr steffenmllr fixed node untar #19 1ded990

There was a bug in the untar function, this should be fixed in v0.1.11 - untar is still relatively slow due to npm/node-tar#23 - I tested the build and the app on a Ubuntu 13.04.

@LifeBeyondTime Would be great if you cloud give it a try


Just tested this, finally saw node-webkit work in ubuntu!
Had to do this on 64-bit:
Due to: cannot open shared object file: No such file or directory

Unpacking can truly take forever, run the task with --verbose to see signs of life


Had the same issue with the shared lib - there are a lot of issues at node webkit eg. nwjs/nw.js#136

It could go a lot faster, if I just stream the download into the gunzip, but that does only work for tar.gz since there is no module out there that supports stream unzipping and permissions: EvanOxfeld/node-unzip#13

I'm working on that...


Thanks @steffenmllr I will try tonight and tell you about the results

gabepaez commented Aug 2, 2014

If this is still an issue please repost to the new parent module

@gabepaez gabepaez closed this Aug 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment