00:58:03  * adrianFquit (Quit: bye)
00:59:28  * timoxleyjoined
01:09:44  * timoxleyquit (Quit: Computer has gone to sleep.)
01:11:48  * timoxleyjoined
01:44:12  * c9botquit (Remote host closed the connection)
01:44:31  * c9botjoined
01:47:40  * timoxleyquit (Quit: Computer has gone to sleep.)
01:49:32  * timoxleyjoined
04:20:14  * eephillipjoined
04:29:25  * eephillipquit (Remote host closed the connection)
07:00:16  * javrubenjoined
07:53:40  * javrubenquit (Quit: javruben)
08:05:22  * javrubenjoined
08:17:28  * flyingmanajoined
09:21:55  * flyingmana__joined
09:25:05  * flyingmanaquit (Ping timeout: 260 seconds)
09:32:07  * dannygjoined
09:35:14  * mAritzjoined
09:36:50  <mAritz>hm, why haven't there been many updates on ajaxorg/cloud9 master?
09:37:16  <mAritz>(just curious, not complaining)
09:38:32  <mAritz>also: is anyone else getting tab crashes in chrome on c9 but not in firefox?
09:40:12  <Chip_Zero>mAritz: we're wokring on a re-arrangement of the Cloud9 OS version. We'll update it as soon as it's done and will keep maintaining it in the future :)
09:40:29  <mAritz>what's the OS version? :D
09:40:37  <mAritz>OSX?
09:41:10  <Chip_Zero>well, open source, i.e. ajaxorg/cloud9 :)
09:41:51  <mAritz>oohh, stupid me :D
09:42:00  <mAritz>ok, cool :)
09:42:57  <mAritz>any idea regarding the tab crashes? i'm trying out c9.io instead of local fork right now, but can't use c9.io that much because the latency on ssh repos is killing me ^^
09:46:33  <Chip_Zero>mAritz: it's a Chrome problem. we're in touch with some of their people, but haven't figured out what is causing it yet. websites should never be able to crash browser tabs, no matter what they do
09:48:10  <Chip_Zero>you can enable crash reporting in the chrome settings, that might help find the cause
09:49:18  <mAritz>oh, didn't know that
09:50:04  <mAritz>i actually am working on a canvas game that at some point crashed my browser tab consistently due to too much ram usage and too many objects created
09:50:23  <mAritz>at least i think that was it, because i reduced both and now it never crashes anymore :D
09:51:06  <mAritz>is it in chrome://settings or in chrome://flags?
09:51:53  <Chip_Zero>it should be in the normal settings, just look for "crash"
09:53:18  <mAritz>my chrome is in german ;D
09:53:23  <mAritz>but i'll try
09:53:39  <Chip_Zero>oh, well, for me it's under privacy
09:54:07  <Chip_Zero>also, afaik it shouldn't crash just because of memory usage. but if you're doing complicated rendering stuff, there might be some bug that crashes it
09:54:09  <mAritz>yep, found it
09:54:10  <mAritz>"Nutzungsstatistiken und Absturzberichte automatisch an Google senden"
09:56:32  <mAritz>i had some bug that literally created billions of objects. i thought it was very sensible of chrome to crash, i probably would'nt have noticed otherwise :D
09:57:32  <mAritz>is there an open issue on gh about the chrome crashes so i can follow it?
10:07:59  <Chip_Zero>you know, I don't think there actually is one
10:08:05  <Chip_Zero>but you can make one
10:23:00  <mAritz>https://github.com/ajaxorg/cloud9/issues/2683 ;)
10:23:02  * timoxleyquit (Quit: Computer has gone to sleep.)
10:23:35  * mikedeboerjoined
10:29:12  <Chip_Zero>excellent
10:30:45  * jkridner_joined
10:32:32  * timoxleyjoined
10:33:58  * jkridnerquit (Ping timeout: 246 seconds)
10:33:58  * jkridner_changed nick to jkridner
11:46:10  * heathquit (Remote host closed the connection)
12:43:13  * heathjoined
12:54:12  * javruben_joined
12:57:43  * javrubenquit (Ping timeout: 260 seconds)
12:57:43  * javruben_changed nick to javruben
13:31:36  * timoxleyquit (Ping timeout: 256 seconds)
13:36:03  * c9botquit (Remote host closed the connection)
13:36:24  * c9botjoined
13:39:05  * javruben_joined
13:39:06  * Peeterquit (Ping timeout: 264 seconds)
13:40:34  * javrubenquit (Ping timeout: 256 seconds)
13:40:34  * javruben_changed nick to javruben
13:49:01  * timoxleyjoined
13:53:40  * Peeterjoined
14:13:55  * timoxleyquit (Quit: Computer has gone to sleep.)
14:15:01  * timoxleyjoined
14:23:53  * timoxleyquit (Quit: Computer has gone to sleep.)
14:58:54  * kladquit
15:02:57  * eephillipjoined
17:04:49  * tongcxjoined
17:05:20  <tongcx>hi, in my terminal, there is a vertical white line, why is that?
17:09:05  * dannygquit (Quit: Leaving.)
17:25:00  * tongcxpart
17:29:26  * javrubenquit (Quit: javruben)
17:40:28  * javrubenjoined
18:57:34  * timoxleyjoined
20:19:08  * timoxleyquit (Quit: Computer has gone to sleep.)
20:23:11  * timoxleyjoined
20:37:45  * timoxleyquit (Quit: Computer has gone to sleep.)
20:38:32  * timoxleyjoined
20:39:52  * timoxleyquit (Client Quit)
21:17:45  * TommehMquit (Excess Flood)
21:26:03  * timoxleyjoined
21:27:06  * TommehMjoined
22:03:28  * tongcxjoined
22:03:51  <tongcx>hi guys, there is a white line in the middle of my terminal on c9, any idea?
22:03:58  <tongcx>a vertical line
22:13:38  * TommehMquit (Excess Flood)
22:18:06  * TommehMjoined
22:32:07  * APLUpart ("Message de d├ępart")
22:38:36  * javrubenquit (Quit: javruben)
22:41:30  <derekjs>tongcx: any chance it's a right margin line or something?
22:43:31  * TommehMquit (Excess Flood)
22:51:36  * TommehMjoined
22:53:31  * mikedeboerquit (Quit: mikedeboer)
23:00:44  * mikedeboerjoined
23:02:56  * mikedeboerquit (Client Quit)
23:06:41  * MerlinDMCquit (Ping timeout: 245 seconds)
23:08:49  * MerlinDMCjoined
23:18:40  * flyingmana__quit (Ping timeout: 260 seconds)