|
Quick Lists
|
|
Bug ID:
|
4546163
|
|
Votes
|
5
|
|
Synopsis
|
OutOfMemoryError is too generic, there should be several with different messages
|
|
Category
|
hotspot:garbage_collector
|
|
Reported Against
|
b03
, hopper
|
|
Release Fixed
|
1.5(tiger)
|
|
State
|
10-Fix Delivered,
request for enhancement
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
4708390
,
6448886
|
|
Submit Date
|
04-DEC-2001
|
|
Description
|
We use OutOfMemoryError to signal several different kinds of out of memory conditions which is confusing to customers. We should have preallocated OutOfMemoryErrors for at the least the following states.
1. General heap full
2. Perm gen full
3. Can't create thread
There may be other cases of this but we should fix these first.
|
|
Work Around
|
N/A
|
|
Evaluation
|
xxxxx@xxxxx 2002-08-15
Yes, this should be done.
|
|
Comments
|
Submitted On 18-JUL-2004
bbatman
Well, thats not all.
A problem that I have with OutOfMemoryError as an application programmer is that there never seems to be a stack trace associated with it; I typically see just
java.lang.OutOfMemoryError
as the sole output when the program crashes.
So, I do not know what line of code caused the condition. It would be nice if you would do at least the minimum amount of processing to supply a stack trace.
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
