Bugzilla – Bug 947911
npm segmentation fault
Last modified: 2015-10-01 09:51:58 UTC
by running npm install -g <package> show: Segmentation fault
The same problem valgrind output. valgrind npm install karma ==8744== Memcheck, a memory error detector ==8744== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==8744== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==8744== Command: /usr/bin/npm install karma ==8744== ==8744== Warning: set address range perms: large range [0x27cdfb052000, 0x27ce1b052000) (noaccess) ==8744== Jump to the invalid address stated on the next line ==8744== at 0x0: ??? ==8744== by 0x6A006A: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) (in /usr/bin/node) ==8744== by 0x6CB431: ??? (in /usr/bin/node) ==8744== by 0x6CB88D: ??? (in /usr/bin/node) ==8744== by 0x27CDFB5060BA: ??? ==8744== by 0x27CDFB8F3DC8: ??? ==8744== by 0x27CDFB519493: ??? ==8744== by 0x27CDFB8F377B: ??? ==8744== by 0x27CDFB519493: ??? ==8744== by 0x27CDFB8F351F: ??? ==8744== by 0x27CDFB8F2FD3: ??? ==8744== by 0x27CDFB519493: ??? ==8744== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==8744== ==8744== ==8744== Process terminating with default action of signal 11 (SIGSEGV) ==8744== Bad permissions for mapped region at address 0x0 ==8744== at 0x0: ??? ==8744== by 0x6A006A: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) (in /usr/bin/node) ==8744== by 0x6CB431: ??? (in /usr/bin/node) ==8744== by 0x6CB88D: ??? (in /usr/bin/node) ==8744== by 0x27CDFB5060BA: ??? ==8744== by 0x27CDFB8F3DC8: ??? ==8744== by 0x27CDFB519493: ??? ==8744== by 0x27CDFB8F377B: ??? ==8744== by 0x27CDFB519493: ??? ==8744== by 0x27CDFB8F351F: ??? ==8744== by 0x27CDFB8F2FD3: ??? ==8744== by 0x27CDFB519493: ??? ==8744== ==8744== HEAP SUMMARY: ==8744== in use at exit: 3,560,597 bytes in 20,207 blocks ==8744== total heap usage: 188,219 allocs, 168,012 frees, 381,793,068 bytes allocated ==8744== ==8744== LEAK SUMMARY: ==8744== definitely lost: 0 bytes in 0 blocks ==8744== indirectly lost: 0 bytes in 0 blocks ==8744== possibly lost: 4,312 bytes in 42 blocks ==8744== still reachable: 3,556,285 bytes in 20,165 blocks ==8744== suppressed: 0 bytes in 0 blocks ==8744== Rerun with --leak-check=full to see details of leaked memory ==8744== ==8744== For counts of detected and suppressed errors, rerun with: -v ==8744== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Killed
. *** This bug has been marked as a duplicate of bug 947747 ***