Bug 1149041

Summary: [abrt] nodejs: node::OnFatalError(): node killed by SIGABRT
Product: [Fedora] Fedora Reporter: M. Edward (Ed) Borasky <znmeb>
Component: nodejsAssignee: T.C. Hollingsworth <tchollingsworth>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: jamielinux, mrunge, sgallagh, tchollingsworth, thrcka, znmeb
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/473402fb596c0563a20f93386a2540cc14eee26d
Whiteboard: abrt_hash:0551b2ddaea7e9853627854edcb8b51cc2f990ab
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-21 21:00:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description M. Edward (Ed) Borasky 2014-10-03 02:47:34 UTC 
Description of problem:
1. Install node.js and npm
2. sudo npm install -g topojson
3. Run topojson from the command line on a huge shapefile - ftp://ftp2.census.gov/geo/tiger/TIGER2014/ZCTA5/tl_2014_us_zcta510.zip
4. It grinds for a long time and then runs out of RAM:

$ topojson -o tl_2014_us_zcta510.topojson tl_2014_us_zcta510.shp
FATAL ERROR: JS Allocation failed - process out of memory
Aborted (core dumped)

I'm going to see if the TopoJSON author has a way to boost the amount of RAM allocated to the JavaScript engine. Meanwhile I have a workaround; there are state-level shapefiles available which are much smaller and will probably not choke topojson / v8. 
 

Version-Release number of selected component:
nodejs-0.10.32-1.fc21

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        node /usr/bin/topojson -o tl_2014_us_zcta510.topojson tl_2014_us_zcta510.shp
crash_function: node::OnFatalError
executable:     /usr/bin/node
kernel:         3.16.3-302.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 node::OnFatalError at ../src/node.cc:1916
 #3 v8::internal::V8::FatalProcessOutOfMemory at src/api.cc:213
 #4 v8::internal::Invoke at src/execution.cc:132
 #5 v8::internal::Execution::Call at src/execution.cc:179
 #6 v8::Function::Call at src/api.cc:3667
 #7 node::MakeCallback at ../src/node.cc:1028
 #9 node::After at ../src/node_file.cc:214
 #10 uv__work_done at ../src/unix/threadpool.c:220
 #11 uv__async_event at ../src/unix/async.c:80
 #12 uv__async_io at ../src/unix/async.c:151
Comment 1 M. Edward (Ed) Borasky 2014-10-03 02:47:37 UTC 
Created attachment 943611 [details]
File: backtrace
Comment 2 M. Edward (Ed) Borasky 2014-10-03 02:47:37 UTC 
Created attachment 943612 [details]
File: cgroup
Comment 3 M. Edward (Ed) Borasky 2014-10-03 02:47:38 UTC 
Created attachment 943613 [details]
File: core_backtrace
Comment 4 M. Edward (Ed) Borasky 2014-10-03 02:47:39 UTC 
Created attachment 943614 [details]
File: dso_list
Comment 5 M. Edward (Ed) Borasky 2014-10-03 02:47:40 UTC 
Created attachment 943615 [details]
File: environ
Comment 6 M. Edward (Ed) Borasky 2014-10-03 02:47:41 UTC 
Created attachment 943616 [details]
File: limits
Comment 7 M. Edward (Ed) Borasky 2014-10-03 02:47:42 UTC 
Created attachment 943617 [details]
File: maps
Comment 8 M. Edward (Ed) Borasky 2014-10-03 02:47:43 UTC 
Created attachment 943618 [details]
File: open_fds
Comment 9 M. Edward (Ed) Borasky 2014-10-03 02:47:43 UTC 
Created attachment 943619 [details]
File: proc_pid_status
Comment 10 M. Edward (Ed) Borasky 2014-10-03 02:47:44 UTC 
Created attachment 943620 [details]
File: var_log_messages
Comment 11 M. Edward (Ed) Borasky 2014-10-03 03:46:24 UTC 
Looks like this has been asked / answered on Stack Overflow

http://stackoverflow.com/questions/16350812/how-to-avoid-topojson-memory-errors#comment23425462_16350812

Go ahead and close this if you wish, or somehow convince abrt that it shouldn't be reported, or fix node so it doesn't dump core and wake up abrt. ;-)
Comment 12 T.C. Hollingsworth 2014-10-21 21:00:02 UTC 
node dumps core on OOM because said core file could be useful to developers finding a memory leak in their code, etc.

ABRT should point people to this bug (and your solution) in the future anyway, so thanks for at least for that.  :-)