Title: No stack trace for OutOfMemoryError
|
Basically, this is normal. I NEVER see a stack trace from an OutOfMemory
exception. Of course, if you think about it, would it be of use? Because it most
probability where you get the OutOfMemory exception is not the actual cause of
the memory leak.
Paul Franz
----- Original Message -----
Sent: Thursday, October 09, 2003 9:50
AM
Subject: [jdjlist] No stack trace for
OutOfMemoryError
We are getting
OutOfMemoryErrors in our app but there is no stack trace. At the time
the Throwable is printed it seems to have sufficient memory (because it opens
a file, prints other info, etc). Does anyone have any ideas why there is no
stack trace? Is it because there isn't sufficient memory to fill the
stack trace when if is created?
Running 1.4.0 on JRun 2.3.3
with 768MB RAM for Java (min and max) an using SoftReferences for soft
caches.
James Stauffer
---
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
---
You are currently subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
|
