https://issues.apache.org/bugzilla/show_bug.cgi?id=40450
Helder Magalhães <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Severity|critical |minor --- Comment #1 from Helder Magalhães <[email protected]> 2009-05-31 01:58:07 PST --- (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 ( https://svn.apache.org/viewcvs.cgi?view=rev&rev=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. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
