DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17820>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17820 Memory leak in resource loader [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2003-10-27 10:54 ------- Thought it would be a singleton. Nice job. That's definitely it, and I can't find any other uses of Runtime in the codebase. This one escaped attention because the DataResourceLoader is not built as part of the standard build due to the j2ee.jar dependency. (And I remember the argument Jason and I had over whether to keep this - I thought it would be a maintenace issue....) It's fixed now, and closing this. Note to interested reader : This does *not* mean that your usage of Velocity is leaking. This was only the DataSourceResourceLoader, and only if you instantiated many many instances of the VelocityEngine. If you don't use the DatasourceResourceLoader, you won't be affected, and if you do, but use Velocity in the canonical way of having one instance for use during the lifetime of your program, you did use up an extra few hundred bytes, and only once. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
