WD hanging with Startwatch

Archive Tinplate Software
1

I downloaded a trial version of startwatch yesterday to stop WD and anything else freezing overnight, but I reported this in the bugs topic earlier. Should startwatch be able to stop this happening? What memory usage would you recommend for WD using startwatch?

The following was in the error report:-

It started with

ERROR: Access violation at address 7C918FEA in module ‘ntdll.dll’. Write of address 00000010 at time/date 05:24:17 22/02/2007

then

Above error or program log occured at :05:24:17 22/02/2007
ERROR: Canvas does not allow drawing at time/date 05:24:17 22/02/2007
Above error or program log occured at :05:24:17 22/02/2007

Above error or program log occured at :05:58:32 23/02/07
ERROR: Error creating window device context at time/date 05:58:33 23/02/07
Above error or program log occured at :05:58:33 23/02/07
ERROR: Error creating window device context at time/date 05:58:34 23/02/07
Above error or program log occured at :05:58:34 23/02/07
ERROR: Error creating window device context at time/date 05:58:35 23/02/07
Above error or program log occured at :05:58:35 23/02/07

and later
ERROR: Out of system resources at time/date 06:57:24 23/02/07
Above error or program log occured at :06:57:24 23/02/07
at time/date 06:57:24 23/02/07
Above error or program log occured at :06:57:24 23/02/07
ERROR: Invalid ImageList Index at time/date 06:57:31 23/02/07
Above error or program log occured at :06:57:31 23/02/07

and yesterdays was the same time and mesage.

thanks.

2

StartWatch should be able to detect program freezes and restart the program when that happens. The memory setting is so dependant on which features of WD you are using, it is hard to make a recommendation for the max memory setting. The best advice is to set it very high or disable it at first. Let WD run for a while (at least 12 hours), and then use the information feature of StartWatch to see what the max memory use was during that time. You can then set the max memory to be 20% to 50% higher than that max value. You don’t want to set this too tight. You just want to catch runaway memory use or long time memory leak cumulative affect. You don’t want StartWatch restarting a program all the time just because it temporarily has memory use peaks.

Steve

3

Thanks Tinplate. I adjusted the settings on startwatch and WD it behaved itself overnight.