|User since||October 27, 2007|
|Number of add-ons developed||0 add-ons|
|Average rating of developer's add-ons||Not yet rated|
Eats CPU Rated 3 out of 5 stars
Nice calendar, however the add-on eats CPU on my old win2k system. On the 300mhz box, I get 5% cpu used when showing just a blank firefox window. Each extra window (that's window not tab) opened uses an *additional* 5%. On faster boxes, you'll get lower numbers, but open 10 or 20 windows and you should see firefox start to appear in the task manager even when idle. I verified this also on a 1.4 Ghz system.
If I had to guess, I would say that the update/refresh increase added to version 1.0.82 is causing it.
There are two problems.
First of all, I'm not displaying the seconds in the add-on, I simply use "%a %b %d". If the user doesn't specify %s or %s, then IMHO the add-on should lower the refresh rate to once per minute or so.
Second, even if I display the seconds the CPU usage shouldn't rise with each open window. If the window is minimized or the add-on doesn't have focus then why bother chewing CPU updating a display that isn't being seen?
Would it be possible to have these two issues fixed? Thanks! :-)