DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40393>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40393 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2006-09-04 23:43 ------- (In reply to comment #0) > The JSVGComponent.loadSVGDocument creates a new Thread to load the specified > document. If too many JSVGComponents are placed on the same page and > initialized > in a loop, this causes creation of too many threads and eventually leads to > OutOfMemory error. It would be nice to have a thread pool of configurable size > (static for the JSVGComponent class). I doubt that the thread pool would help much. In all likelyhood you are just running out of memory. If you haven't already I would suggest increasing the default memory allocation in the JDK. Also since we restrict ourself to JDK 1.3 we would either have the create our own thread pool or add a dependency on another java library (I suppose Apache Avalon or the like must have one). Since I'm fairly convinced that the number of threads is not the real issue I am reluctant to do this. If you can provide good evidence that the problem is the threads rather than the memory needed to display lots of SVG images feel free to reopen. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
