00:09:32  * paulbjensenjoined
00:43:18  <paulbjensen>@sberryman - sorry I disappeared last night before saying goodbye, sleep got me
00:45:27  <sberryman>paulbjensen: no problem, most of the memory leak was around PDF but I think there is still something leaking slowly but I didn't have time to look into it last night
00:46:08  <paulbjensen>cool, when you say PDF is it anything to do with imagemagick?
00:46:25  <sberryman>nope
00:46:31  <paulbjensen>because we used it at work, and found that occasional PDFs would make it bork
00:46:51  <sberryman>i moved all of it into another process that I just execute from within node
00:47:25  <sberryman>5375 www 57 0 178M 154M 0 S 0.0 24.2 1:03.28 /opt/local/bin/node app.js
00:47:48  <sberryman>much smaller right now and it starts at around 8-11% so it doubled in about 24 hours
00:48:34  <sberryman>lets say I have the following: `ss.http.route("/", function (req, res) { res.serveClient("main"); })`
00:48:55  <sberryman>if a user hits `/` vs `/test` vs `/abc` does that have any impact?
00:49:22  <sberryman>i know everything gets served to the client directly but does the initial path make a difference to assets and what gets stored in memory?
00:50:45  <paulbjensen>SS's http route acts like a catch all, which is bad because you can't return 404s for missing assets
00:51:11  <sberryman>it also has problems with newrelic's nodejs monitoring
00:51:25  <paulbjensen>we need to fix it here: https://github.com/socketstream/socketstream/issues/286
00:51:45  <paulbjensen>Yeah, funny enough they sent me a ticket asking me to contact them about it
00:51:59  <paulbjensen>an email I should say
00:52:16  <sberryman>no kidding? i tried it out yesterday or the day before and no bueno
00:52:44  <paulbjensen>it was ~ 4 hours ago
00:53:37  <paulbjensen>I'll deal with it tomorrow
00:53:59  <sberryman>it might be because i tried to deploy and it started reporting data to newrelic and their website showed a bunch of errors when I tried to view that app, i'm sure that showed up in their logs and maybe they dug in
00:56:04  <paulbjensen>Interesting, not sure what would cause them to incur an error.
00:56:26  <sberryman>they do some strange injection into express i believe
00:56:45  <sberryman>or connect
01:02:10  <paulbjensen>that could be it. gtg now, have a good evening
01:02:14  * paulbjensenquit (Quit: paulbjensen)
01:44:23  * evangenieurquit (Remote host closed the connection)
01:44:57  * evangenieurjoined
01:49:45  * evangenieurquit (Ping timeout: 272 seconds)
02:01:04  * mdedetrichquit (Quit: Computer has gone to sleep.)
03:43:38  * mdedetrichjoined
03:48:03  * mdedetrichquit (Max SendQ exceeded)
03:49:38  * mdedetrichjoined
03:50:20  * mdedetrichquit (Client Quit)
04:44:50  * mdedetrichjoined
04:49:49  * mdedetrichquit (Quit: Computer has gone to sleep.)
06:07:51  * mal```quit (Ping timeout: 260 seconds)
06:17:55  * mdedetrichjoined
06:18:53  * mal``joined
06:21:16  * lluadquit (Quit: lluad)
07:12:45  * sberrymanquit (Read error: Connection reset by peer)
07:42:42  * mdedetrichquit (Quit: Computer has gone to sleep.)
08:31:17  * evangenieurjoined
09:17:58  * evangenieurquit (Remote host closed the connection)
09:18:33  * evangenieurjoined
09:22:50  * evangenieurquit (Ping timeout: 256 seconds)
09:37:12  * paulbjensenjoined
11:48:10  * mdedetrichjoined
11:51:34  * mal``quit (Read error: Connection reset by peer)
11:59:22  * mal``joined
12:08:46  * mdedetrichquit (Quit: Computer has gone to sleep.)
12:48:30  * paulbjensenquit (Quit: paulbjensen)
13:24:17  * paulbjensenjoined
16:04:22  * lluadjoined
17:22:55  * paulbjensenquit (Quit: paulbjensen)
17:57:33  * dennismartenssonjoined
18:18:18  * dennismartenssonquit
21:20:40  * mdedetrichjoined
22:47:24  * mdedetrichquit (Quit: Computer has gone to sleep.)
23:20:12  * mdedetrichjoined
23:24:58  * mdedetrichquit (Quit: Computer has gone to sleep.)
23:57:25  * mdedetrichjoined