Program slows down when left running
Brought to you by:
cyberfox
I leave JBidwatcher running continuously monitoring my
auctions. After a few days, it is noticably slower to
use through the GUI. Adding auctions, adding snipe
amounts, deleting auctions are all slower and seem to
demand more CPU resource. A simple restart of the
program sorts it out but then of course it happens
again over a few days.
Could this be a memory problem or a problem with
traversing long lists in the cache?
BTW a super program I couldn't live without.
MAC OSX 10.4.2
david.frith@bigfoot.com
Logged In: NO
Yes, exactely the same, and the need to force quit when everything seem
working (slow) :(item or tab browsing) but ?Q (Quit) don't.
Logged In: YES
user_id=19745
Originator: NO
Greetings,
Bugs filed before 1.0 and bugs without responders are being juggled in terms of priority (9 is highest priority). I'm raising bugs filed with a submitter, post-1.0 to P6. Bugs which are filed post-1.0, but without a submitter are P5. Before 1.0 bugs with a submitter are becoming P4, and pre-1.0 bugs without a submitter name become P3.
If the bug is still relevant, and has a watcher (i.e. you got notified when I changed this bug), feel free to bubble it back up again.
Email addresses in bugs are great, but I can't always respond via email. Sometimes, especially for duplicate bugs, I use automated tools (like I'm doing right now) to change status on a large number of items at once.
Thanks for your patience, while I try to pare back the bug list to what may actually still be in the program.
-- Morgan Schweers, CyberFOX!