Name: gm110360			Date: 08/08/2003


FULL PRODUCT VERSION :
java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21)
Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode)

FULL OPERATING SYSTEM VERSION :
Microsoft Windows 2000 [Version 5.00.2195]


A DESCRIPTION OF THE PROBLEM :
When running javaw (ie double clicking an executable jar) if
the program runs out of memory, no indication is given.  It
simply hangs in an indeterminant state leaving the user to
decide something is wrong.  Notification with a popup would
be a sufficient solution (until garbage collection improves
greatly).

This is a particularly bad issue for programs that have long
computationally intensive initialisations

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Launch any program with an artificially small maximum
stack size in javaw.
2. Watch it freeze.

EXPECTED VERSUS ACTUAL BEHAVIOR :
If run using java instead of javaw, at least "Exception in
thread "main" java.lang.OutOfMemoryError" is displayed.

REPRODUCIBILITY :
This bug can be reproduced often.

CUSTOMER WORKAROUND :
Launch with larger maximum stack size.  Not a viable option
for applications launched by double-clicking.
(Incident Review ID: 179122) 
======================================================================