Name: tb29552 Date: 11/19/98


1. Launch java.exe with or without a class file (a LOT more noticeable WITH a GUI
class) (Same applies to javaw.exe, and jre.exe from earlier JDK releases)
2. No source code required
3. No error messages reported by JRE
4.

Install BoundsChecker from www.numega.com. This program detects memory
leaks and resource leaks and other problems with 32bit windows executable programs.

Load java.exe, or javaw.exe into BoundsChecker

Specify a class to execute on the command line settings inside BoundsChecker.

Run the program from within BoundsChecker.

When the java.exe program terminates, MANY
MEMORY LEAKS and MANY RESOURCE LEAKS are reported.

Typically, with a minimal UI class we are seeing approximately 50
memory leaks and more importantly for us 20 Windows resource leaks.

5. We are a UK government agency working on a project which requires prolonged
use of the JRE over a period of many hours with many stops and restarts of the Java
virtual machine during normal business processes.

We are currently investigating a problem which we believe to be attributed to the
Windows platform losing resources over an extended period of time (i.e. 8, 9, 10
hours) During this period, the Java application is being re-invoked typically every
five minutes by 90 users.

The system gets progressively slower, and then finally crashes in the jre.exe
or an associated dll.

Addressing this problem is CRUCIAL to our use of Java within the agency. We are
currently running LIVE and MUST have a solution to this problem.
(Review ID: 43035)
======================================================================