Re: Netscape 7.1 memory leaks

Dennis wrote:

Garbage collection is a low-priority task. You're creating new objects at
the rate of one a second over an hour. Netscape probably never bothers to
do any garbage collection until the browser is more "idle" then you are
allowing it to be at any point during the execution. As a result it just
continues to request memory from the operating system (which the operating
system is happy to provide up to and beyond the amount of physical memory
present on the system). Once you exceed the amount of physical memory
available, the operating system will begin to swap and you will have
serious performance problems.

Do you really want everyone using that page to be making requests to your
Web server every second? Since you never display the image I'm guessing
you're using it as some sort of "keep alive" session management or
something? HTTP through a Web browser isn't really the proper medium for
something that requires knowing if the client is connected every second.
You're trying to drive a nail with a screwdriver.

the example provided is designed to accelerate the problem so it
happens in a half hour rather than a day.

Being able to "drive a nail with a screwdriver" has earned me a pretty
good living, and its what sets apart the men from the boys in the
programming field. Bad programmers make excuses; Good programmers find
solutions.

And shysters use unreliable hacks to achieve a result until their hack comes unglued, then they blame their
tools.

Your management or customers aren't going to care how you got
something done, only that the end result works well, is intuitive and
doesnt cause a 2Ghz machine to run like an IBM XT (ie Java). It helps,
of course, when the tools work as expected.

They also expect it to work long-term and not break with the latest release of the latest "gee whiz" browser.

--

Grant Wagner <gwagner (AT) agricoreunited (DOT) com

* Client-side Javascript and Netscape 4 DOM Reference available at:
* http://devedge.netscape.com/library/...ce/frames.html
* Internet Explorer DOM Reference available at:
* http://msdn.microsoft.com/workshop/a...ence_entry.asp
* Netscape 6/7 DOM Reference available at:
* http://www.mozilla.org/docs/dom/domref/
* Tips for upgrading JavaScript for Netscape 7 / Mozilla
* http://www.mozilla.org/docs/web-deve...upgrade_2.html

Grant Wagner <gwagner (AT) agricoreunited (DOT) com> wrote

Dennis wrote:

Garbage collection is a low-priority task. You're creating new objects at
the rate of one a second over an hour. Netscape probably never bothers to
do any garbage collection until the browser is more "idle" then you are
allowing it to be at any point during the execution. As a result it just
continues to request memory from the operating system (which the operating
system is happy to provide up to and beyond the amount of physical memory
present on the system). Once you exceed the amount of physical memory
available, the operating system will begin to swap and you will have
serious performance problems.

Do you really want everyone using that page to be making requests to your
Web server every second? Since you never display the image I'm guessing
you're using it as some sort of "keep alive" session management or
something? HTTP through a Web browser isn't really the proper medium for
something that requires knowing if the client is connected every second.
You're trying to drive a nail with a screwdriver.

the example provided is designed to accelerate the problem so it
happens in a half hour rather than a day.

Being able to "drive a nail with a screwdriver" has earned me a pretty
good living, and its what sets apart the men from the boys in the
programming field. Bad programmers make excuses; Good programmers find
solutions.

And shysters use unreliable hacks to achieve a result until their hack comes unglued, then they blame their
tools.

Your management or customers aren't going to care how you got
something done, only that the end result works well, is intuitive and
doesnt cause a 2Ghz machine to run like an IBM XT (ie Java). It helps,
of course, when the tools work as expected.

They also expect it to work long-term and not break with the latest release of the latest "gee whiz" browser.

I would say that sabotaging a design that will work on 95% of machines
to accommodate those stupid enough to use "gee-whiz" browsers is the
one whos making the mistake. If you'd rather stand by your square
wheel and pound your chest that it "fits any car" good for you, but my
round wheel is going to blow yours away. Product design is about
making money; about having a better product, not about making
universally mediocre widgets.

You really dont have a point because Im not trying to do anything out
of spec. Nor am I trying to drive a nail with a screwdriver. Netscape
just has a plethora of problems, as they always have. We all know it,
so why are you agruing against it?