Hi all,

I’ve been using jbidwatcher forever… it’s an awesome app. However, over the last couple of weeks I’ve noticed that it at times becomes unresponsive when I try and bring it to focus from the system tray. When it’s in this state it also doesn’t fire any snipes.

In these cases I end up having to end task javaw.exe from the task manager and at that point the memory usage is usually around 500MB (it’s normally 20MB-40MB).

Once I do that I can restart the app & it works ok… for awhile.

I’m using 2.0beta8 under xp pro. I haven’t determined if it’s a gradual climb to all that memory or if something triggers it to use it all at once – I have jbid startup with my login & usually leave it active all the time.

I just started using jbidwatcher. I’m on a Mac, same exact version of jbidwatcher, 2.0beta8, on Mac OS10.4.11 (Tiger).
For comparison I just opened Activity Monitor to see if this is happening on Mac too. I have Word 2004, Firefox 3, and Jbidwatcher now open. {Word with no doc open]

CPU        Real Memory             Virtual Memory
Firefox,           4-18%     81 MB                        254 MB
Word 2004,     2-6%      55 MB                        218 MB
JBidwatcher,    6-18%    69 MB                        861 MB

Other than kernel-task, which I think is the system software which uses 1 GB of vitual memory, nothing is close to jbidwatcher in that category.

What this means I don’t know, but I hope this helps you to know if this is a bug.
Frank