All times are UTC.
00:16:52 <-- Kaishi has quit (Quit: Kaishi) 00:36:11 <-- mconley has quit (Ping timeout) 00:52:21 <-- mpmc has quit (Connection reset by peer) 01:03:25 <-- rosonline has quit (Quit: Instantbird 1.3 -- http://www.instantbird.com) 01:29:09 --> mconley has joined #instantbird 02:24:35 <-- FireFly_TB has quit (Ping timeout) 02:51:51 <instant-buildbot> build #826 of linux-nightly-default is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/linux-nightly-default/builds/826 02:55:55 --> jb has joined #instantbird 02:56:26 <-- jb has quit (Excess Flood) 03:14:49 --> FireFly_TB has joined #instantbird 03:33:20 <instant-buildbot> build #822 of macosx-nightly-default is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/macosx-nightly-default/builds/822 03:58:13 --> zen_monkey has joined #instantbird 04:56:55 --> jb has joined #instantbird 05:01:11 <-- jb has quit (Ping timeout) 05:14:28 <instant-buildbot> build #918 of win32-nightly-default is complete: Success [build successful] Build details are at http://buildbot.instantbird.org/builders/win32-nightly-default/builds/918 06:13:35 <-- mconley has quit (Ping timeout) 06:29:01 <-- zen_monkey has quit (Quit: Saliendo) 07:22:09 --> Kaishi has joined #instantbird 08:09:13 <-- FireFly_TB has quit (Ping timeout) 08:36:29 --> jb has joined #instantbird 08:54:53 <-- jb has quit (Input/output error) 08:54:57 --> jb has joined #instantbird 09:05:48 <-- jb has quit (Ping timeout) 09:37:50 --> FireFly_TB has joined #instantbird 09:39:31 <-- FireFly_TB has quit (Ping timeout) 09:57:12 --> jb has joined #instantbird 09:57:15 <-- jb has quit (Excess Flood) 09:57:18 --> jb has joined #instantbird 10:03:58 <-- jb has quit (Ping timeout) 10:13:36 --> mpmc has joined #instantbird 10:22:28 --> jb has joined #instantbird 10:22:28 <-- jb has quit (Excess Flood) 10:22:34 --> jb has joined #instantbird 10:44:55 --> FireFly_TB has joined #instantbird 10:50:48 <-- Tonnes has quit (Quit: ChatZilla 0.9.90 [Firefox 19.0.2/20130307023931]) 10:54:21 <-- jb has quit (Ping timeout) 10:54:40 --> aleth has joined #instantbird 10:54:40 * ChanServ sets mode +h aleth 11:16:01 --> Even has joined #instantbird 11:16:01 * ChanServ sets mode +o Even 12:23:35 --> jb has joined #instantbird 12:25:23 <-- FireFly_TB has quit (Ping timeout) 12:39:53 --> jb1 has joined #instantbird 12:39:59 <-- jb has quit (Connection reset by peer) 12:55:46 --> Tonnes has joined #instantbird 13:53:37 <aleth> I rather like this icon from Gaia (apart from maybe the odd shadow) https://mxr.mozilla.org/gaia/source/apps/sms/style/icons/Sms.png 13:55:29 <flo-retina> it looks to me like a knob to control the volume on a stereo :-S 13:56:02 <aleth> Heh, true. (It's not an icon for an app, it's for incoming SMS notifications) 13:57:11 <aleth> Or maybe it is the icon for the SMS app? :-S 13:57:34 <aleth> I saw it next to the message text, so the meaning was clear there. 14:49:23 <-- jb1 has quit (Ping timeout) 14:52:30 <aleth> Is it common that unprefixed CSS attribute values behave differently from the prefixed version, without the prefixed version generating a warning? 14:53:33 <aleth> Just tracked down a bug that seems to be caused by this. 14:53:56 <aleth> (for -moz-fit-content and fit-content) 15:02:25 <-- Optimizer has quit (Connection reset by peer) 15:05:25 <aleth> Hmm, -moz-linear-gradient differs from linear-gradient in syntax, so maybe issues like this are not so rare. 15:06:02 <flo-retina> aleth: the reason why the prefix exists is that the syntax isn't definitive yet 15:07:00 <aleth> flo-retina: I realise this, but I was under the impression that usually by the time the prefix was dropped the syntax or meaning would have stabilised. 15:21:32 <aleth> Doh, in this case it's just that fit-content hasn't been unprefixed yet. But the corresponding warning got lost somehow. 15:24:40 --> Optimizer has joined #instantbird 15:43:17 --> FireFly_TB has joined #instantbird 15:51:16 --> mikk_s has joined #instantbird 15:51:40 <-- mikk_s has quit (Quit: Instantbird 1.3 -- http://www.instantbird.com) 16:03:58 <-- gerv has quit (Ping timeout) 16:04:19 --> gerv has joined #instantbird 16:13:42 <-- mpmc has quit (Connection reset by peer) 17:16:51 --> skeledrew has joined #instantbird 17:25:28 <-- Optimizer has quit (Ping timeout) 17:40:17 <-- aleth has quit (Quit: Ciao) 17:40:25 --> aleth has joined #instantbird 17:40:26 * ChanServ sets mode +h aleth 17:58:33 * flo-retina hopes https://bugzilla.mozilla.org/show_bug.cgi?id=856443 will be useful 18:04:23 <aleth> Nice job tracking that down :) 18:04:35 --> gerard-majax__ has joined #instantbird 18:05:02 <-- gerard-majax_ has quit (No route to host) 18:06:32 <flo-retina> I like that we now have tools to track it down when Firefox is using an additional GB of memory than usual :) 18:06:58 <aleth> DMD is a special build, not just a command line flag on debug builds, right? 18:08:13 <flo-retina> it's a non-debug build with --enable-dmd at configure time 18:09:05 <flo-retina> now the tool I would really like to have, is a way to know what's using memory in JS code 18:10:00 <flo-retina> it doesn't help me much to know that imConversations.js is currently using 2.9MB 18:10:22 <flo-retina> it would be nice to know where objects that are still alive / are expensive were allocated (there would likely be surprises!) 18:11:16 <aleth> Yes, that would be nice. Even just to see which objects are still around. 18:11:44 <flo-retina> there's likely a lot of junk that could be cleaned up 18:12:06 <aleth> We are bound to be unintentionally keeping things 18:13:49 <flo-retina> jsProtoHelper is blamed for 1.57MB, including 0.43MB of strings 18:14:45 <flo-retina> having about:memory outputs from people who keep Ib running without restarting for a week or more would likely be interesting (that's how we detected that twitter leak :)) 18:19:27 <aleth> yes, it's one thing we don't do much, as nightly users. 18:20:53 <flo-retina> my Ib currently takes 278MB 18:20:55 <flo-retina> that seems a lot 18:21:20 <flo-retina> but I don't see anything obvious in about:memory 18:21:48 <flo-retina> or maybe we should just unload from memory the old messages and reload them if the user scrolls 18:28:55 <aleth> Is most of the memory usage the actual conversation browser DOM content or is it evenly split between that and the associated conversations? 18:30:33 <flo-retina> aleth: http://pastebin.mozilla.org/2262800 18:32:11 <flo-retina> aleth: a closer look at the most expensive instantbird.xul sub-window: http://pastebin.mozilla.org/2262804 18:32:51 <aleth> Can't see anything that looks particularly surprising there either. 18:33:37 <flo-retina> the only obvious possible saving I see is avoiding all the style= in Bubbles 18:34:01 <flo-retina> that's likely the cause of most of 0.86 MB (00.45%) ââ style-contexts, 0.33 MB (00.17%) ââ rule-nodes, 0.17 MB (00.09%) ââ style-sets 18:34:35 <aleth> Didn't you already try that once and it slowed things down? 18:34:41 <flo-retina> yeah 18:35:02 <flo-retina> I tried that because parsing the style= stuff was showing up in the profiler 18:35:10 <flo-retina> but I was likely trying too many things at once ;) 18:38:02 <flo-retina> iirc I had completely rewritten the HTML code to make it easy to insert the buddy icons next to the bubble arrows 18:38:17 <flo-retina> it's possible my new HTML/CSS code was more expensive to paint 18:41:54 --> Mic has joined #instantbird 18:41:54 * ChanServ sets mode +h Mic 19:00:58 <-- FireFly_TB has quit (Ping timeout) 19:02:38 <-- aleth has quit (Quit: Ciao) 19:11:04 <-- Mic has quit (Quit: No time to waste, let's go!) 19:17:43 --> FireFly_TB has joined #instantbird 19:31:20 <-- FireFly_TB has quit (Ping timeout) 20:07:10 --> Optimizer has joined #instantbird 20:36:02 --> Mic has joined #instantbird 20:36:03 * ChanServ sets mode +h Mic 20:40:45 <Mic> Hi 20:59:26 --> FireFly_TB has joined #instantbird 21:46:20 <-- FireFly_TB has quit (Ping timeout) 22:18:04 <-- instant-buildbot has quit (Input/output error) 22:19:59 --> instant-buildbot has joined #instantbird 22:19:59 * ChanServ sets mode +v instant-buildbot 22:56:46 <-- Mic has quit (Quit: No time to waste, let's go!)