#941 S L O W D O W N... High RAM use

[Anonymous]

I'm seeing the same problem that some others are, the
PC that runs Jbidwatcher slows down until finally it
has to be rebooted. I need to reboot about 1 time per
day to keep reasonably normal performance.

My system: W2Ksp4 fully patched, 1GB RAM, Athlon 3000+
Barton, Jbidwatcher 1.0pre6, Sun Java 1.5.0_06-b05.

In looking at the taskmanager, javaw.exe's memory use
grows to about .5GB when I start feeling like I have to
reboot. If I terminate Jbidwatcher and run a RAM
defragmenter like AnalogX Maxmem in agressive mode, it
gets better but not as good as if I reboot the system.

How many auctions I have in tabs also seems to affect
how quickly the problem occurs. I have started keeping
things cleaned out, even though that affects how useful
the program is.

Feel free to contact me if you need additional details.
I'll run any tests that you think would be useful.

rob dot |>
huston at |>> Just to keep the bots
rindahl dot |>> at bay... :)
com |>

[Morgan Schweers]

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!