Bug 40450 - OutofMemory Exception swallowed.
Summary: OutofMemory Exception swallowed.
Status: NEEDINFO
Alias: None
Product: Batik - Now in Jira
Classification: Unclassified
Component: Bridge (show other bugs)
Version: 1.6
Hardware: PC Windows XP
: P2 minor
Target Milestone: ---
Assignee: Batik Developer's Mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-08 18:16 UTC by John Fleenor
Modified: 2009-05-31 01:58 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Fleenor 2006-09-08 18:16:05 UTC 
A bad image link was displayed with no errors, when I actually recieved a 
OutOfMemoryException. The OutOfMemoryExpception is swallowed by a catch 
(Throwable t) at line 105 in the 
org.apache.batik.ext.awt.image.codec.png.PNGRegistryEntry:105
Comment 1 Helder Magalhães 2009-05-31 01:58:07 UTC 
(In reply to comment #0)
> A bad image link was displayed with no errors, when I actually recieved a 
> OutOfMemoryException. The OutOfMemoryExpception is swallowed by a catch 
> (Throwable t) at line 105 in the 
> org.apache.batik.ext.awt.image.codec.png.PNGRegistryEntry:105

Yes, I confirmed this (though it is in line 113 as of Batik 1.8pre - revision 777417). Nevertheless, I'm not sure what should happen instead: remove that catch block, maybe? In that case, what about other exceptions (I/O, thread death, etc.)?

I'd say this could be marked invalid as the OOM exception seems to be the actual problem (incorrect dimensioning of the JVM memory)... Marking as need info in order to call for feedback. ;-)  Also, please consider marking as invalid if you feel (like I do) that the swallowing the exception is at least coherent with other exceptions being handled in a "best-effort" fashion.