nodejs crashed with SIGABRT - out of memory
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nodejs (Ubuntu) |
New
|
Medium
|
Unassigned | ||
Bug Description
Trying to install parchment https:/
"FATAL ERROR: JS Allocation failed - process out of memory
Aborted (core dumped)"
alan@deep-
Cloning into 'parchment'...
remote: Reusing existing pack: 2971, done.
remote: Total 2971 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (2971/2971), 4.42 MiB | 960.00 KiB/s, done.
Resolving deltas: 100% (1579/1579), done.
Checking connectivity... done.
alan@deep-
alan@deep-
npm http GET https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm WARN prefer global grunt-cli@0.1.13 should be installed with -g
grunt-cli@0.1.13 node_modules/
├── resolve@0.3.1
├── nopt@1.0.10 (abbrev@1.0.4)
└── findup-sync@0.1.3 (lodash@2.4.1, glob@3.2.9)
alan@deep-
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http GET https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http 304 https:/
npm http GET https:/
npm http 304 https:/
npm http 200 https:/
FATAL ERROR: JS Allocation failed - process out of memory
Aborted (core dumped)
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: nodejs 0.10.25~
ProcVersionSign
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 31 21:50:54 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nodejs
InstallationDate: Installed on 2012-06-29 (640 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: npm
Signal: 6
SourcePackage: nodejs
StacktraceTop:
?? ()
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: nodejs crashed with SIGABRT
UpgradeStatus: Upgraded to trusty on 2014-01-20 (70 days ago)
UserGroups: adm autopilot cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo
| Alan Pope 🍺🐧🐱 🦄 (popey) wrote | #1 |
| Apport retracing service (apport) wrote | #2 |
| Apport retracing service (apport) wrote Stacktrace.txt | #3 |
| Apport retracing service (apport) wrote StacktraceSource.txt | #4 |
| Apport retracing service (apport) wrote ThreadStacktrace.txt | #5 |
| Changed in nodejs (Ubuntu): | |
| importance: | Undecided → Medium |
| tags: | removed: need-amd64-retrace |
| information type: | Private → Public |
StacktraceTop:
node::OnFatalError (location=
v8::internal:
v8::internal:
v8::internal:
v8::internal: