#3 Clicksaver consumes all available memory on startup
The very first time I started clicksaver up, it seemed to
work okay, it said it's DB was out of date and went
about building itself a new one. After it seemed to be all
done doing that, I shut the program down and went and
did something else for awhile.
Some time later, I set AO to run in windowed mode and
started it up, got my character to a mission terminal and
then started up Clicksaver. My computer then proceeds
to absolutely choke. Every available bit of memory is
dumped into clicksaver, the pagefile is maxed and I get a
little system error window saying that I am now out of
virtual memory. Clicksaver itself never decides to show
up past the splash screen. After a few minutes of
waiting for Task Manager to finally show up, I'm finally
able to kill Clicksaver and my system returns to normal.
After a reboot, I try just starting up Clicksaver by itself,
with no AO running and my task manager already open
so I can see what it actually does. After starting
Clicksaver, it tries to consume all available memory and
processor cycles again, making my system memory
usage go from about 155,424K / 1,493,572K to pretty
much full. It manages to do this with almost no (in this
case 6) I/O reads for a grand total of 283 bytes read
and 0 written. I'm not exactly a PhD, but I'm reasonably
certain there's some sort of error that's not being
checked thats resulting in some infinite loop of memory
eating.
Since it may help, these are the specs on my system:
AMD 1.0Ghz Athlon, 768 MB ram
Win2k with SP4 and the latest version of DirectX (9.0a)
Radeon 7500
MS Intellimouse (I saw a bug relating to Logitech drivers,
so I'd like you to know that it's not that)
If you need to know more about my system, just email
me.
