Comments for hskupin.info http://www.hskupin.info Mozilla, Photography and the Daily Life Mon, 07 May 2012 23:02:25 +0000 hourly 1 http://wordpress.org/?v=3.3.2 Comment on Mozmill 1.5.12 released by Henrik Skupin http://www.hskupin.info/2012/05/07/mozmill-1-5-12-released/comment-page-1/#comment-12760 Henrik Skupin Mon, 07 May 2012 23:02:25 +0000 http://www.hskupin.info/?p=911#comment-12760 You are welcome. Important issues have to be fixed ASAP. Good to see that I was able to bring tests for Thunderbird back to life again! You are welcome. Important issues have to be fixed ASAP. Good to see that I was able to bring tests for Thunderbird back to life again!

]]> Comment on Mozmill 1.5.12 released by Mike Conley http://www.hskupin.info/2012/05/07/mozmill-1-5-12-released/comment-page-1/#comment-12759 Mike Conley Mon, 07 May 2012 22:57:37 +0000 http://www.hskupin.info/?p=911#comment-12759 Henrik: On behalf of the whole Thunderbird team, thanks so much for your work this weekend! -Mike Henrik:

On behalf of the whole Thunderbird team, thanks so much for your work this weekend!

-Mike

]]> Comment on MemChaser 0.3 is out by Henrik Skupin http://www.hskupin.info/2012/04/07/memchaser-0-3-is-out/comment-page-1/#comment-12645 Henrik Skupin Mon, 09 Apr 2012 17:41:46 +0000 http://www.hskupin.info/?p=884#comment-12645 That's correct. If you can still see issues when you compile the extension against the SDK 1.6 please comment on <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=726485" rel="nofollow">bug 726485</a>. That’s correct. If you can still see issues when you compile the extension against the SDK 1.6 please comment on bug 726485.

]]> Comment on MemChaser 0.3 is out by ferongr http://www.hskupin.info/2012/04/07/memchaser-0-3-is-out/comment-page-1/#comment-12632 ferongr Sat, 07 Apr 2012 14:46:12 +0000 http://www.hskupin.info/?p=884#comment-12632 The fix for the leaking cuddlefish.js compartments landed in release 1.6 of the Add-on SDK, right? The fix for the leaking cuddlefish.js compartments landed in release 1.6 of the Add-on SDK, right?

]]> Comment on MemChaser 0.2 released by Henrik Skupin http://www.hskupin.info/2012/03/02/memchaser-0-2-released/comment-page-1/#comment-12507 Henrik Skupin Thu, 08 Mar 2012 14:35:38 +0000 http://www.hskupin.info/?p=873#comment-12507 Yamaban, it's great to hear that it was helpful for you even in such an early state. We are planning way more stuff to integrate into future releases of MemChaser. So keep an eye on our project page and if questions or issues arise don't hesitate to contact us. Would be great if you could also give a review on AMO for MemChaser. Thanks. Yamaban, it’s great to hear that it was helpful for you even in such an early state. We are planning way more stuff to integrate into future releases of MemChaser. So keep an eye on our project page and if questions or issues arise don’t hesitate to contact us. Would be great if you could also give a review on AMO for MemChaser. Thanks.

]]> Comment on MemChaser 0.2 released by yamaban http://www.hskupin.info/2012/03/02/memchaser-0-2-released/comment-page-1/#comment-12506 yamaban Thu, 08 Mar 2012 14:27:55 +0000 http://www.hskupin.info/?p=873#comment-12506 Thanks for the work you put into memchaser. In concert with profiles that differ only in extensions, I could track down most of my issues much faster than ever before. Even memory issues related to long-time running Fx and many open tabs where now much easier to track. Most fun is to use the same set of extensions and tabs open and view memusage over time. Great work is done on the recent nightlies (this last week). E.g. start FX, rmem[160MB] load tab-set (all) rmem[310MB], let is sit idle for two hours, switch trough all tabs rmem[260MB]. Much better than mid January (can't prof this, lost some data). Thanks again for the work. Thanks for the work you put into memchaser.

In concert with profiles that differ only in extensions, I could track down most of my issues much faster than ever before.

Even memory issues related to long-time running Fx and many open tabs where now much easier to track.

Most fun is to use the same set of extensions and tabs open and view memusage over time. Great work is done on the recent nightlies (this last week).
E.g. start FX, rmem[160MB] load tab-set (all) rmem[310MB], let is sit idle for two hours, switch trough all tabs rmem[260MB]. Much better than mid January (can’t prof this, lost some data).

Thanks again for the work.

]]> Comment on MemChaser – An extension to track Firefox’s memory activities by Henrik Skupin http://www.hskupin.info/2012/02/10/memchaser-an-extension-to-track-firefoxs-memory-activities/comment-page-1/#comment-12485 Henrik Skupin Mon, 05 Mar 2012 07:31:54 +0000 http://www.hskupin.info/?p=866#comment-12485 Ben, good to hear. When you say that you are able to determine the reason for ui hangs, what are those in specific? Has there been filed a bug on Bugzilla for it already? Ben, good to hear. When you say that you are able to determine the reason for ui hangs, what are those in specific? Has there been filed a bug on Bugzilla for it already?

]]> Comment on MemChaser 0.2 released by Henrik Skupin http://www.hskupin.info/2012/03/02/memchaser-0-2-released/comment-page-1/#comment-12484 Henrik Skupin Mon, 05 Mar 2012 07:12:19 +0000 http://www.hskupin.info/?p=873#comment-12484 We currently don't have any control on the font settings in the widget. But a fix has already been checked in for Add-ons SDK 1.6. So we only will have to wait for. Also see our own <a href="https://github.com/mozilla/memchaser/issues/62" rel="nofollow">tracking issue</a>. Re: missing tooltips, we already have an <a href="https://github.com/mozilla/memchaser/issues/60" rel="nofollow">issue</a> on our milestone 0.3 list to get those implemented for each of the entries. Given the pressure we had with 0.2 there was simply no time to get it implemented. And no, we don't want to use a panel for that. Those are not tooltips. We currently don’t have any control on the font settings in the widget. But a fix has already been checked in for Add-ons SDK 1.6. So we only will have to wait for. Also see our own tracking issue.

Re: missing tooltips, we already have an issue on our milestone 0.3 list to get those implemented for each of the entries. Given the pressure we had with 0.2 there was simply no time to get it implemented. And no, we don’t want to use a panel for that. Those are not tooltips.

]]> Comment on MemChaser 0.2 released by pd http://www.hskupin.info/2012/03/02/memchaser-0-2-released/comment-page-1/#comment-12477 pd Sun, 04 Mar 2012 07:50:08 +0000 http://www.hskupin.info/?p=873#comment-12477 The font-size should be adjustable or just respect the host OS font size. The values don't mean anything. XXXms (XXs) ... Please give the values title attributes or labels or something. Better still, how about a Jetpack panel? https://addons.mozilla.org/en-US/developers/docs/sdk/latest/packages/addon-kit/docs/panel.html The font-size should be adjustable or just respect the host OS font size.

The values don’t mean anything. XXXms (XXs) …

Please give the values title attributes or labels or something. Better still, how about a Jetpack panel?

https://addons.mozilla.org/en-US/developers/docs/sdk/latest/packages/addon-kit/docs/panel.html

]]> Comment on MemChaser – An extension to track Firefox’s memory activities by Ben Ryan http://www.hskupin.info/2012/02/10/memchaser-an-extension-to-track-firefoxs-memory-activities/comment-page-1/#comment-12471 Ben Ryan Sat, 03 Mar 2012 09:15:08 +0000 http://www.hskupin.info/?p=866#comment-12471 Hah. That nailed my problem...thanks guys. Great tool. I'm getting gc:~600ms / cc:~1700ms times... till now I couldn't determine the cause of the UI hangs - now I can. Cheers Hah. That nailed my problem…thanks guys. Great tool.
I’m getting gc:~600ms / cc:~1700ms times… till now I couldn’t determine the cause of the UI hangs – now I can.
Cheers

]]> Comment on How I fixed a Mozmill freeze by bisecting Python by Henrik Skupin http://www.hskupin.info/2012/02/08/how-i-fixed-a-mozmill-freeze-by-bisecting-python/comment-page-1/#comment-12459 Henrik Skupin Wed, 29 Feb 2012 05:38:11 +0000 http://www.hskupin.info/?p=826#comment-12459 Interesting. So we never were able to nail down this problem when you have mentioned it? Where has it been got stuck? Have we filed a bug for Mozmill? Interesting. So we never were able to nail down this problem when you have mentioned it? Where has it been got stuck? Have we filed a bug for Mozmill?

]]> Comment on How I fixed a Mozmill freeze by bisecting Python by ilya http://www.hskupin.info/2012/02/08/how-i-fixed-a-mozmill-freeze-by-bisecting-python/comment-page-1/#comment-12458 ilya Wed, 29 Feb 2012 02:35:14 +0000 http://www.hskupin.info/?p=826#comment-12458 That is what I've been talking about last year when I was writing test using MozmillRestart class That is what I’ve been talking about last year when I was writing test using MozmillRestart class

]]> Comment on MemChaser – An extension to track Firefox’s memory activities by Stephan Sokolow http://www.hskupin.info/2012/02/10/memchaser-an-extension-to-track-firefoxs-memory-activities/comment-page-1/#comment-12401 Stephan Sokolow Tue, 14 Feb 2012 12:04:14 +0000 http://www.hskupin.info/?p=866#comment-12401 I used to run Chrome on the beta channel but, for Firefox, I don't trust upgrading and downgrading to leave my profile in a usable state so I stay on the release channel. My main concern is that, since this takes some time to build up, if I make a copy of my profile to test on Aurora or Nightly, I might accumulate state that could take a while to track down and copy back into my stable profile. (eg. bookmarks injected by StumbleUpon, etc.) Since I'm already a bit behind in my French course, I'm not sure when I'll have time to take that risk. I am definitely looking forward to when release catches up with the minimum requirements of some of the performance-analysis extensions for Aurora and Nightly though. I used to run Chrome on the beta channel but, for Firefox, I don’t trust upgrading and downgrading to leave my profile in a usable state so I stay on the release channel.

My main concern is that, since this takes some time to build up, if I make a copy of my profile to test on Aurora or Nightly, I might accumulate state that could take a while to track down and copy back into my stable profile. (eg. bookmarks injected by StumbleUpon, etc.)

Since I’m already a bit behind in my French course, I’m not sure when I’ll have time to take that risk.

I am definitely looking forward to when release catches up with the minimum requirements of some of the performance-analysis extensions for Aurora and Nightly though.

]]> Comment on MemChaser – An extension to track Firefox’s memory activities by Henrik Skupin http://www.hskupin.info/2012/02/10/memchaser-an-extension-to-track-firefoxs-memory-activities/comment-page-1/#comment-12395 Henrik Skupin Mon, 13 Feb 2012 11:26:12 +0000 http://www.hskupin.info/?p=866#comment-12395 @Stephan: Which version of Firefox are you using? Is it an Aurora or even Nightly build? If yes you should probably comment on <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=725110" title="Bug 725110" rel="nofollow">. Sounds like you are also affected by this bug. Doing a log with MemChaser for about 1h and attaching it beside the comment would also be helpful. There are some tools available and with the MemChaser project we want to make those more easily accessible. In general it really depends on what you are looking for and is probably worth another blog post (from the JS devs). I would say lets start with your issue from top and find out more in incremental steps. So please check out the bug I have mentioned. Thanks for your feedback!</a> @Stephan: Which version of Firefox are you using? Is it an Aurora or even Nightly build? If yes you should probably comment on . Sounds like you are also affected by this bug. Doing a log with MemChaser for about 1h and attaching it beside the comment would also be helpful.

There are some tools available and with the MemChaser project we want to make those more easily accessible. In general it really depends on what you are looking for and is probably worth another blog post (from the JS devs).

I would say lets start with your issue from top and find out more in incremental steps. So please check out the bug I have mentioned. Thanks for your feedback!

]]> Comment on MemChaser – An extension to track Firefox’s memory activities by Caspy7 http://www.hskupin.info/2012/02/10/memchaser-an-extension-to-track-firefoxs-memory-activities/comment-page-1/#comment-12392 Caspy7 Sun, 12 Feb 2012 21:17:19 +0000 http://www.hskupin.info/?p=866#comment-12392 I at that issue for the tooltip. It would be a very ugly thing to do, but, if it's possible, perhaps copying and pasting the full list of helpful text into the widget tooltip would still make the addon overall more usable. Just an interim, workaround thought. I at that issue for the tooltip.
It would be a very ugly thing to do, but, if it’s possible, perhaps copying and pasting the full list of helpful text into the widget tooltip would still make the addon overall more usable.
Just an interim, workaround thought.

]]>