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