What steps will reproduce the problem? 1. This seems to happen when the widget has been loaded in the Dashboard for a while (weeks), whether or not it has been used heavily
What is the expected output? What do you see instead?
The widget becomes unresponsive, eventually taking over the CPU. The remedy is to force quit the widget from Activity Monitor.
What version of the product are you using? On what operating system?
0.9.6.1b
Please provide any additional information below.
The most likely culprit is the animation code for expanding/collapsing the widget. There may be a setInterval that is not being cleared properly and recursively spawning processes.
Comment #1
Posted on Mar 27, 2008 by Quick KangarooAs all code was rewritten, it's unlikely that this issue will continue to exist.
Status: WontFix
Labels:
Type-Defect
Priority-Medium