[1418] in java-interest
RE: java-interest-digest V1 #138
daemon@ATHENA.MIT.EDU (muzo)
Fri Sep 1 15:05:19 1995
Date: Thu, 31 Aug 95 17:12:17 UT
From: "muzo " <MuzoK@msn.com>
To: "Robert Stephen Rodgers" <rsrodger@wam.umd.edu>
Cc: "'java-interest@java.sun.com'" <java-interest@java.sun.com>
I was responding to the statement which looked to me like this was a problem
only for Windows OS. Especially by mentioning the resource problem of win3.1
you made it sound like (to me at least) that this leaky process problem was
specific to Windows/Win32. My understanding is that if a process is leaking
resources, whatever kind they may be, the OS will either run out of those
resources
at some point or will have to kill that process when it runs out
of its quota or the process
will exit because it can't get any more
resources of some kind. I believe this is not
specific to a single family of
OSs.
muzo
----------
From: owner-java-interest@java.sun.com on behalf
of Robert Stephen Rodgers
Sent: Thursday, August 31, 1995 5:02 AM
To:
muzo
Cc: 'java-interest@java.sun.com'
Subject: RE: java-interest-digest
V1 #138
> Also as HotJava is a 32 process the problem of multiple runs of
it leaking
> memory is gone too. Under Win32 (win95 and NT, 2 current
implementations) if the
> process doesn't leak any resources,
Well,
yes, but what I'm referring to is processes that _do_.
RSR
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
