Hi
I tested these 2 modes (both housekeeper and console processes
disabled) and found the runtime error to be reproducible as before.
Strangely, failure occured about 30% earlier than usual (2 hours
instead of 3, 800,000 cycles instead of 1.2 million).
This doesn't necessarily mean anything at all. Although failure
usually occurs around the same point (3-4 hrs), I've had exceptions
where it can occur after only 1 hour or not until 5. Thats how
slippery this problem is. The only consistent thing is that it
definitely always occurs at some point.
b.t.w. the test platform is a brand new machine with only 'out of the
box' stuff running on it + 4D. The production environment is also
reasonably clean but it does have a virus checker running.
Issue tracker, debug application and readme document have all been
updated appropriately.
Regards
Peter
On 17 Oct 2010, at 05:47, Aparajita Fishman wrote:
There are two variables left to test.
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
