Hi Rob -- sorry for the really late reply -- it seems that there is a hitch in my receiving the daily digest from this group and I had to reset stuff today.
I have not followed the memory usage lately any more, but will let you know if I can follow it in the future. Meanwhile, if only we could get rid of the Safari auto-open bug.... (I am using 10.6.8, and the problem repeats with beta 63 and the old safari plugin after I installed and ran beta 64 with the updated safari plugin). On Jan 20, 2:57 pm, Rob McBroom <[email protected]> wrote: > On Jan 20, 2012, at 2:10 PM, R wrote: > > > I think that there is a bug in the new version of the plugin because > > of the following problem. QS seems to be accumulating real and virtual > > memory with time. For example, I was listening to itunes all through > > the morning and yesterday evening/night and QS became unresponsive > > around noon today. I checked and found that it was using >1GB real > > (and ~idential virtual) memory. I have restarted it but the memory use > > seems to be slowly going up (from 38MB starting to about 42MB in about > > 10 mins). I'll repost if I see the same behavior being replicated. In > > the meantime, I hope this heads-up helps if there is a real problem. > > Hmm. I haven’t seen anything like this, but as you can imagine, I end up > restarting Quicksilver every few minutes for various development tasks so it > never has a chance to leak a lot of memory. > > Can you tell me more specifically what you were doing? Were you actively > picking and playing things all morning via Quicksilver, or just letting it > play in the background? Do you have Quicksilver set to monitor recent tracks? > > If you continue to see this, could you try disabling the iTunes plug-in and > restarting Quicksilver just to make sure that’s the source of the memory > increase? Thanks. > > -- > Rob McBroom > <http://www.skurfer.com/>
