nwjc crashed on macOS 10.13.2
See original GitHub issueNWJS Version : 0.27.0 Operating System : macOS 10.13.2
Expected behavior
compile successful.
Actual behavior
<unknown>:1510427: Invalid asm.js: Unexpected token
Received signal 11 SEGV_MAPERR 000000000010
==== C stack trace ===============================
[0x00010b928f34]
[0x7fff7863df5a]
[0x7fab39413320]
[0x7fff783bc115]
[end of stack trace]
[1] 21482 segmentation fault
How to reproduce
nwjc some.js some.bin
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
MacOS High Sierra 10.13.2 causing Finder crash
I have a MacBook Pro (Retina, Mid 2012) running Os X version 10.13.2 (17C88) and I have the same issue. I never experienced...
Read more >Word 2016 keeps crashing, Mac High Sierra 10.13.2
Hi, I have been having lots of trouble with Microsoft word recently. If my file contains too much information (i.e lots of equations...
Read more >Mac crash: why it happens and how to fix it - MacPaw
Here're the most common reasons why your Mac keeps restarting: Application incompatibility. The system crash can be the “reaction” of your macOS ...
Read more >macOS 10.13 High Sierra Compatibility Info
Note: If using a different version of macOS, see the Latest OS Compatibility article. With UAD-2 and Apollo hardware, UAD software v9.4...
Read more >Downloads - iTerm2 - macOS Terminal Replacement
3.14.7 - Rebuild using macOS Ventura SDK. - Fix crash on macOS 10.15 when using eyedropper. - Fix bug where transparency is lost...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks,
--no-validate-asm
works for me.For me, I was including a
.bin
compiled file of.js
while doing development. Switching from.bin
to correct.js
file solved the issue.