| || |
Silk 5.0/Netscape 4 memory leak
If you are encountering intermittent/strange failures during
long (3+ hours) test runs using Silk 5.0 and one of the Netscape 4
browsers (4.08 or 4.51) you are likely running out of
memory. I have finally tracked this problem down, under NT 4.0. This
problem does not appear to occur using Navigator 3.04 gold.
The problem is obvious once ALL of physical memory is consumed,
as you get virtual memory error dialog. But it is not at all apparent
as you get close to exhausting memory (ah, those boundry conditions, eh?).
The cause of the virtual memory error is Navigator -- it slowly
consumes all of available memory, which appears to be a memory leak
problem. But its not clear to me if Navigator is the real culprit or
the Silk Agent's integration with Navigator. I have logged a problem
with Segue support.
-fyi, Terry Horwath
The Carl Group
Re: Silk 5.0/Netscape 4 memory leak
Netscape's 4.x browsers are prone to memory leaks standing by themselves. On more than one occasion, I've left a Netscape browser open overnight or over the weekend, doing absolutely nothing but sitting on a home page and it's eaten up all available memory. It is possible that working these browsers in conjunction with Silk accelerates this process.