Tough question. We haven't been testing the 4.0.4pl1 as much, but the
behavior doesn't seem to found there. Mind you this could be due to a
lack of complete testing on our part. I will see if it's possible to
revert back to 4.0.4pl1 and try some more, but judging by the past
occurances, the ear
Is this a new issue in 4.0.5? Or did the problem exist in older versions
as well?
Zeev
At 18:44 21/3/2001, Dan Kalowsky wrote:
>Follow up on the earlier reporting of having memory issues to 4.0.5RC1.
>
>We've been able to reproduce the problem once again. Although it seems
>to be only happeni
Follow up on the earlier reporting of having memory issues to 4.0.5RC1.
We've been able to reproduce the problem once again. Although it seems
to be only happening after EXTREMELY long periods of time and continuous
heavy usage during that time. Currently I'm not able to point exactly
to any sp
