Posting in these forums is disabled. These forums will be available for archive purposes. Please join the new forums at the links below:

  • yui-support - replaces the `YUI 3.x` and `YUI 3 Gallery` forums.
    We have created the following discussion categories within this group to aid discoverability for these most-used topics:
    • Charts for YUI Charts support.
    • DataTable for YUI DataTable support.
    • Gallery for YUI Gallery support, including support for published Gallery components as well as the Gallery process in general.
    • Tools for support of YUI’s suite of developer tools such as selleck, shifter, grover, yogi, etc.
    • Everything Else for questions that don’t fit one of the categories above, we’ve got you covered here.
  • yui-deprecated - replaces the `YUI 2.x` forum and the forums of other deprecated products (`YUI Doc`, `Builder`, `YUI PHP Loader`, etc.).
  [ 1 post ]
New Topic | Post Reply | Print view
Previous topic | Next topic


  • Username: garamoi
  • Joined: Thu Aug 04, 2011 10:22 am
  • Posts: 1
  • Offline
  • Profile
  • Lion
  • crash
  • node
  • server
  • yeti

server mode running on OSX Lion ...

Post Posted: Thu Aug 04, 2011 11:09 am
I have installed yeti recently via npm (assuming the most recent version) on a OSX Lion system. I am seeing regular crashes by just running the server only, so am wondering if there are any issues I should be aware of when running yeti on Lion.

I just ran the server :

[testSys1:~/yui3_3] testSys1% yeti --server
Yeti will only serve files inside /Users/testSys1/yui3_3
Visit http://localhost:8000, then run:
yeti <test document>
to run and report the results.

I just let the server run for a while (without initiating any request from a yeti client), and it crashes after a while (15 - 20 min.) with a crash log reported as follows:

(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
at EventEmitter.<anonymous> (events.js:126:17)
at wait (/Users/testSys1/node_modules/yeti/lib/server.js:106:15)
at Object.<anonymous> (/Users/testSys1/node_modules/yeti/lib/server.js:141:9)
at nextMiddleware (/Users/testSys1/node_modules/yeti/node_modules/express/node_modules/connect/lib/middleware/router.js:175:25)
at param (/Users/testSys1/node_modules/yeti/node_modules/express/node_modules/connect/lib/middleware/router.js:183:16)
at pass (/Users/testSys1/node_modules/yeti/node_modules/express/node_modules/connect/lib/middleware/router.js:191:10)
at Object.router [as handle] (/Users/testSys1/node_modules/yeti/node_modules/express/node_modules/connect/lib/middleware/router.js:197:6)
at next (/Users/testSys1/node_modules/yeti/node_modules/express/node_modules/connect/lib/http.js:198:15)
at Object.bodyParser [as handle] (/Users/testSys1/node_modules/yeti/node_modules/connect/lib/middleware/bodyParser.js:76:7)
at next (/Users/testSys1/node_modules/yeti/node_modules/express/node_modules/connect/lib/http.js:198:15)

Has anyone experienced this kind of crashes on a OSX system, especially on Lion?
  [ 1 post ]
New Topic | Post Reply | Print view
Previous topic | Next topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum