ddopson / underscore-cli

Command-line utility-belt for hacking JSON and Javascript.
Other
1.73k stars 83 forks source link

100% cpu with node 0.9.9 #15

Open whyman opened 11 years ago

whyman commented 11 years ago

Not sure why, but it just hangs.

$ uname -a Linux hostname 3.7.1-gentoo #1 SMP Fri Jan 11 09:07:52 GMT 2013 x86_64 Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz GenuineIntel GNU/Linux

$ node -v v0.9.9

$ npm -v 1.2.10

$ npm -g ls -> /usr/lib64 /usr/lib ├── coffee-script@1.4.0 ├─┬ connect@2.7.3 │ ├── buffer-crc32@0.1.1 │ ├── bytes@0.2.0 │ ├── cookie@0.0.5 │ ├── cookie-signature@0.0.1 │ ├── debug@0.7.2 │ ├── formidable@1.0.11 │ ├── fresh@0.1.0 │ ├── pause@0.0.1 │ ├── qs@0.5.1 │ └─┬ send@0.1.0 │ ├── mime@1.2.6 │ └── range-parser@0.0.4 ├─┬ handlebars@1.0.9 │ ├─┬ optimist@0.3.5 │ │ └── wordwrap@0.0.2 │ └── uglify-js@1.2.6 ├─┬ jshint@0.9.1 │ ├─┬ cli@0.4.3 │ │ └─┬ glob@3.1.20 │ │ ├── graceful-fs@1.2.0 │ │ ├── inherits@1.0.0 │ │ └─┬ minimatch@0.2.9 │ │ ├── lru-cache@2.0.4 │ │ └── sigmund@1.0.0 │ └─┬ minimatch@0.0.5 │ └── lru-cache@1.0.6 ├─┬ less@1.3.3 │ └── ycssmin@1.0.1 ├─┬ npm@1.2.10 │ ├── abbrev@1.0.4 │ ├── ansi@0.1.2 │ ├── archy@0.0.2 │ ├── block-stream@0.0.6 │ ├── chownr@0.0.1 │ ├── fstream@0.1.22 │ ├─┬ fstream-npm@0.1.3 │ │ └── fstream-ignore@0.0.6 │ ├── glob@3.1.19 │ ├── graceful-fs@1.2.0 │ ├── inherits@1.0.0 │ ├── ini@1.1.0 │ ├─┬ init-package-json@0.0.6 │ │ └── promzard@0.2.0 │ ├── lockfile@0.3.0 │ ├── lru-cache@2.0.4 │ ├─┬ minimatch@0.2.9 │ │ └── sigmund@1.0.0 │ ├── mkdirp@0.3.4 │ ├── node-gyp@0.8.4 │ ├── nopt@2.1.1 │ ├─┬ npm-registry-client@0.2.13 │ │ └── couch-login@0.1.15 │ ├─┬ npmconf@0.0.23 │ │ └─┬ config-chain@1.1.5 │ │ └── proto-list@1.2.2 │ ├── npmlog@0.0.2 │ ├── once@1.1.1 │ ├── opener@1.3.0 │ ├── osenv@0.0.3 │ ├─┬ read@1.0.4 │ │ └── mute-stream@0.0.3 │ ├── read-installed@0.1.1 │ ├── read-package-json@0.1.13 │ ├── request@2.9.203 │ ├── retry@0.6.0 │ ├── rimraf@2.1.4 │ ├── semver@1.1.3 │ ├── slide@1.1.3 │ ├── tar@0.1.16 │ ├── uid-number@0.0.3 │ └── which@1.0.5 ├─┬ recess@1.1.6 │ ├── colors@0.6.0-1 │ ├─┬ less@1.3.3 │ │ └── ycssmin@1.0.1 │ ├─┬ nopt@2.1.1 │ │ └── abbrev@1.0.4 │ ├── underscore@1.4.4 │ └── watch@0.5.1 ├─┬ uglify-js@2.2.5 │ ├─┬ optimist@0.3.5 │ │ └── wordwrap@0.0.2 │ └─┬ source-map@0.1.8 │ └── amdefine@0.0.4 └─┬ underscore-cli@0.2.16 ├── coffee-script@1.4.0 ├─┬ commander@1.1.1 │ └── keypress@0.1.0 ├── JSONSelect@0.4.0 ├── msgpack@0.1.7 ├── underscore@1.4.4 └── underscore.string@2.3.1

ddopson commented 11 years ago

Hmm, can we repro this on any other platform? Does it still repro with the latest version?

I think this might have been fixed with the latest version (which addressed issues for Node v0.10.x).