00:28:34  * mdedetrichjoined
01:13:11  <sberryman>anyone around?
01:58:29  * paulbjensenjoined
01:58:31  <paulbjensen>Yes
01:58:48  <sberryman>hey! thanks for pickup back up maint on ss by the way
01:59:05  <paulbjensen>you're welcome
01:59:51  <sberryman>quick question for ya.. why in the world would my app take up a ton of memory in production? i'm assuming it is attempting to load everything into memory?
02:00:44  <sberryman>34153 www 1 0 278M 251M 0 S 0.0 39.3 0:06.35 /opt/local/bin/node app.js
02:00:51  <paulbjensen>good question, what version of SS are you running?
02:01:12  <sberryman>just deployed off the master branch about 2 hours ago
02:01:58  <paulbjensen>Has your app been running for only 6 minutes?
02:02:15  <sberryman>nah, that is cpu time
02:03:29  <paulbjensen>How long has the process been running?
02:03:39  <sberryman>1 hour and 28 minutes
02:04:21  <sberryman>sorry, that is the start timestamp.. it's been a long day :) it has been running for 31 minutes at 18 seconds
02:05:05  <paulbjensen>what is the memory value now? I'm beginning to think that this is a memory leak
02:05:54  <sberryman>it has decreased a bit: 34153 www 1 0 271M 244M 0 S 1.0 38.2 0:06.81 /opt/local/bin/node app.js
02:06:23  <sberryman>pretty sure there has been a steady memory leak but i never took the time to pinpoint it (i would just restart the process every night at 10pm)
02:07:51  <sberryman>http://imgur.com/xJeLtuV
02:07:58  <sberryman>that is the past 7 days
02:10:58  <sberryman>if i had to guess though it would be in the package i use to generate pdf's as the memory leak
02:12:55  <paulbjensen>is the pdf generator a separate process, or part of the same process?
02:13:03  <sberryman>same
02:13:59  <paulbjensen>I can suggest 2 possible ways to diagnose it
02:14:11  <sberryman>listening :)
02:14:15  <paulbjensen>1st one is to generate a flame graph
02:14:21  <paulbjensen>alternatively, use node-inspector
02:15:51  <paulbjensen>links: http://blog.nodejs.org/2012/04/25/profiling-node-js/, https://github.com/node-inspector/node-inspector, https://github.com/felixge/node-memory-leak-tutorial
02:16:06  <sberryman>yeah, was already reading about flame graph
02:20:46  * evangenieurquit (Remote host closed the connection)
02:21:20  * evangenieurjoined
02:25:43  * evangenieurquit (Ping timeout: 246 seconds)
02:39:33  * paulbjensenquit (Quit: paulbjensen)
04:01:19  * danfojoined
07:09:34  * mdedetrichquit (Quit: Computer has gone to sleep.)
07:29:29  * danfoquit (Quit: danfo)
07:32:21  * mdedetrichjoined
07:43:01  * mdedetrichquit (Quit: Computer has gone to sleep.)
11:06:56  * danfojoined
11:09:19  * danfoquit (Client Quit)
11:12:47  * danfojoined
11:34:18  * evangenieurjoined
12:12:50  * mdedetrichjoined
12:36:20  * mdedetrichquit (Quit: Computer has gone to sleep.)
12:49:55  * evangenieurquit (Remote host closed the connection)
12:50:30  * evangenieurjoined
12:55:02  * evangenieurquit (Ping timeout: 246 seconds)
12:58:59  * kurovajoined
13:03:31  * kurovaquit (Remote host closed the connection)
13:08:01  * danfoquit (Quit: danfo)
13:11:09  * danfojoined
14:23:20  * danfoquit (Quit: danfo)
15:03:41  * sberrymanquit (Read error: Connection reset by peer)
15:58:51  * lluadjoined
16:03:10  * espacejoined
16:10:26  * manyacooljoined
16:34:49  * sberrymanjoined
17:03:50  * manyacoolquit (Read error: Connection reset by peer)
17:04:21  * espacequit (Ping timeout: 272 seconds)
18:21:30  * AviMarcusjoined
20:05:07  * AviMarcusquit (Quit: Ex-Chat)
20:29:48  * firealejoined
20:55:39  * firealequit (Read error: Connection reset by peer)
21:40:59  * evangenieurjoined
22:21:43  * mdedetrichjoined
23:02:44  * mdedetrichquit (Quit: Computer has gone to sleep.)
23:14:08  * mdedetrichjoined
23:24:09  * lluad_joined
23:25:58  * lluadquit (Ping timeout: 245 seconds)
23:25:58  * lluad_changed nick to lluad