Netscape v7.0 and memory build-up

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Eugene
    #1

    Netscape v7.0 and memory build-up

    Hi all,

    I have a page that uses JavaScript to continuously reload an image
    (Client-Pull method). Using Netscape v7.0 on Windows NT 4, Service
    Pack 6a, the images reload fine, but using Performance Monitor or even
    Task Manager, I notice that the Commited Bytes In Use of the Memory
    steadily climbs and after some time, it suddenly drops to about where
    it started.

    The link to the page is here:
    http://www.rtww.co.za/streaming_muizenberg.html

    and the JavaScript source is available by viewing the HTML source.

    My question is: Is this memory build-up behaviour normal to Netscape,
    because using Internet Explorer v6 to view the same page, I see no
    memory buidl-up at all? Can this cycle of build-up and releasing of
    virtual memory be explained by the JavaScript Garbage Collection
    implementation of Netscape? If so, why does the memory usage of IE6
    remain constant, since it also implements Garbage Collection? Is
    there perhaps a recursive allocating of new memory in my script? If
    not, is there a way for me to stop the memory build-up when using
    Netscape?

    Many thanks for any comments or suggestions.

    Eugene
    (eugene@ccii.co .za)
    Tags: None
    • Oopman
      #2
      Re: Netscape v7.0 and memory build-up

      Eugene wrote:[color=blue]
      > Hi all,
      >
      > I have a page that uses JavaScript to continuously reload an image
      > (Client-Pull method). Using Netscape v7.0 on Windows NT 4, Service
      > Pack 6a, the images reload fine, but using Performance Monitor or even
      > Task Manager, I notice that the Commited Bytes In Use of the Memory
      > steadily climbs and after some time, it suddenly drops to about where
      > it started.[/color]

      Why are you using this javascript if an easy html meta refresh would do
      the job?
      [color=blue]
      > The link to the page is here:
      > http://www.rtww.co.za/streaming_muizenberg.html[/color]

      Cool!
      [color=blue]
      > and the JavaScript source is available by viewing the HTML source.
      >
      > My question is: Is this memory build-up behaviour normal to Netscape,
      > because using Internet Explorer v6 to view the same page, I see no
      > memory buidl-up at all? Can this cycle of build-up and releasing of
      > virtual memory be explained by the JavaScript Garbage Collection
      > implementation of Netscape? If so, why does the memory usage of IE6
      > remain constant, since it also implements Garbage Collection? Is
      > there perhaps a recursive allocating of new memory in my script? If
      > not, is there a way for me to stop the memory build-up when using
      > Netscape?[/color]

      In my humble experience, the combi NS & java is kind of buggy... that's
      why I prefer a meta-refresh in plain html.
      [color=blue]
      >
      > Many thanks for any comments or suggestions.
      >
      > Eugene
      > (eugene@ccii.co .za)[/color]

      Hoped I was of any assitance,
      Michael,
      The Netherlands.

        Comment

        Previous template Next
        Working...