Illegal Instruction in NodeJS

[iamrecursion]

It seems that sticking around alpine edge is turning up all sorts of bugs! This one is quite simple to reproduce, but I can provide a rootfs if necessary.

1. Set your repositories to alpine edge.
2. apk add nodejs
3. Run node.

It will crash with an illegal instruction that boils down to the following:

50 illegal instruction at 0x56d4d529: 0f 72 f0 01 8b 00 66 0f

Output from `dmesg` for the crash

[    0.000000] 50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 383
               50 stub syscall 375
               50 illegal instruction at 0x56d4d529: 0f 72 f0 01 8b 00 66 0f 
               56 stub syscall 383
               56 stub syscall 383
               56 stub syscall 383
               56 stub syscall 383
               56 stub syscall 383
               56 stub syscall 383

[62f]

Shocking that after 'switching the repositories' from 3.12? to >3.12 and using "apk add", that the first thing I'd purposefully-omit= apk update & apk upgrade

[zerkotin]

All i get is “illegal instruction” when running either node or npm

[Askovia]

In case you haven't fixed it, I manage to fix it in my phone by also installing npm along with nodejs, since they are codependent

[zerkotin]

I have both installed on my iPad and it doesn’t work, when calling both npm or node i get Illegal Instruction

[zerkotin]

Update:
I updated and upgraded apk like so:
apk update
apk upgrade
Then removed node and npm
apk del nodejs
apk del npm
Then reinstalled them
apk add nodejs
apk add npm
Now it works - seems like the new apk updates adds and installs dependent libraries necessary to run it
node runs like a dream :)
You can close the ticket as far as im concerned.

Thank you (it took a while) but thank you.

[Askovia]

Also noticed that the error comes when you aren't running the AppStore Repos

[specious]

None of these proposed solutions are helping. Any advice on how to investigate what is causing this crash?

[specious]

iSH needs SSE2 instruction support: #90 (comment)

[specious]

This is the problem: #1473

[Ivan0x17]

"Node and npm" return
illegal instruction

Probably the problem is nodejs why npm It depends on nodejs and v8 javascript engine

Does anyone have a solution??

[iamrecursion]

Wait until the next AppStore release.

[Ivan0x17]

Wait until the next AppStore release.

Ok 👍🏻, thank you so much for fast response about my question, good project!! , I hope to use node-red soon

[Diluka]

any updates?

[mfyz]

+1

[pro-gamer007]

+2

[saagarjha]

We don't really need votes for this issue, it's already been fixed and will ship in the next release.

[pro-gamer007]

When will the next release be?

[remino]

When is the next release?

[luni-moon]

I’m getting the same issue on the most recent edge branch of Alpine, and after updating and upgrading, and installing the pkgs with —-no-cache, it broke nodejs and npm. None of the solutions said to work above, worked on my local device. Any help would be appreciated! Thanks!

EDIT: I did some research, and was told the following tag would work, but the--jitless flag has virtually no effect, as seen here:

# node --jitless src/index.js
Warning: disabling flag --expose_wasm due to conflicting flags
Illegal instruction

According to the NODEJS Documentation, --jitless is to:

Disable runtime allocation of executable memory. This may be required on some platforms for security reasons. It can also reduce attack surface on other platforms, but the performance impact may be severe.

This flag is inherited from V8 and is subject to change upstream.
It may disappear in a non-semver-major release.

And according to v8.dev, it is supposed to make NODEJS work on iOS devices, as seen in point number one:

But in some situations it can be desirable to run V8 without allocating executable memory:

1. Some platforms (e.g. iOS, smart TVs, game consoles) prohibit write access to executable memory for non-privileged applications, and it has thus been impossible to use V8 there so far; and
2. disallowing writes to executable memory reduces the attack surface of the application for exploits.

So, this flag should be able to work to make NODEJS to work on iSH, but it doesn’t. This could be a great starting point though for ideas.

[vkhv]

+1

[famiclone]

Any updates?

[TheGhostboi64]

I’m also getting the same problem

[vkhv]

Does anyone know how to run node.js on ipad? Another way

[specious]

Look at #1482.

[Fonysony]

#1482 Actually works, just had to use vim to switch the repo into 1.12 and download node 12.22.12-r0. One issue is that it doesn't run well at times.

[saagarjha]

iSH 1.3 is out, which has fixes for this issue. Please try it out and file new issues with what you encounter!

[dishanaik]

iSH 1.3 is out, which has fixes for this issue. Please try it out and file new issues with what you encounter!

Whoa! Finally. Thanks