On 25/03/2010 12:13 PM, Bob Lee wrote:
On Thu, Mar 25, 2010 at 8:55 AM, [email protected]
<mailto:[email protected]> <[email protected]
<mailto:[email protected]>> wrote:
On Mar 25, 6:30 am, cowwoc <[email protected]
<mailto:[email protected]>> wrote:
> [...] I don't like the fact that you've chosen to ship the
> product with a pretty sizable memory leak and no decent workaround.
Umm... the decent workaround is to restart your application when you
redeploy.
This is not a viable solution for debugging web applications. Some
servers take over a minute to restart. In the past I had to issue a
restart every two runs because I'd run out of memory. This is a huge
productivity killer.
+1
I'll fix it eventually. My fix will only work on specific VM's, of
course, as it'll depend on private APIs.
So why not bite the bullet and add a shutdown method? There are
plenty of APIs with dispose() methods. Isn't this more reasonable than
resorting to complicated voodoo that only works for a subset of your
users? Seeing as you work for Google, why not ask Joshua Bloch for advice?
Gili
--
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-guice?hl=en.
