[1363] in java-interest
RE: java-interest-digest V1 #138
daemon@ATHENA.MIT.EDU (muzo)
Thu Aug 31 03:32:17 1995
Date: Thu, 31 Aug 95 03:36:32 UT
From: "muzo " <MuzoK@msn.com>
To: "'java-interest@java.sun.com'" <java-interest@java.sun.com>,
"Robert
Stephen Rodgers" <rsrodger@wam.umd.edu>
the resource leak problem under previous versions of windows was caused by OS
not
cleaning up after a program exited. For various moronic reasons, the OS
doesn't mark
all the resources allocated by a process as such and when it
exists can't GC them.
It is not a matter of a single process running
continuously and leaking resources with no
fault of the process. 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, the OS doesn't do it by itself and any
and all resources which
the process didn't clean up, get deallocated when
the process exists unlike win31
muzo
----------
From:
owner-java-interest@java.sun.com on behalf of Robert Stephen Rodgers
Sent:
Wednesday, August 30, 1995 5:51 AM
To: java-interest@java.sun.com
Cc:
java-interest-digest@java.sun.com
Subject: Re: java-interest-digest V1 #138
Java becomes popular on Windows
Users have Java programs that they might
like open most of the time
I'm not quite sure how Java interacts with
Windows 95, having only run a2 for
NT, but I'm concerned about the
following:
On Windows 95, long term resource leaks. These are not
pointers! They are
pointer-like (in that somewhere the system has allocated
memory to them)
"handles." Windows 95, in case anyone missed it, still
carries some of the
extremely bone-headed resource problems that afflicted
prior Windows versions.
Creating a permanent resource drain is a bad thing
if Java is to succeed.
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
