Interestingly the problem only seems to occur with frames. If I take
away the
frame the problem goes away.
My page is deliberately allocating a lot of memory, but I thought the
memory was
supposed to be automatically freed by Javascript garbage collection.
Any thoughts on how to get around this problem (which seems to happen
with
Netscape but not with Internet Explorer)? Thanks,
- Mitch
- mgart at netegrity dot com