When performing a refresh I've read that the cache gets dumped. I've noticed after a refresh the reference counts to objects don't go down. Basically the entire cache seems to be leaked. Is this by design or is it a bug? -- Dylan Jay --- http://www.meetmemap.com - makes giving directions easy http://www.pretaweb.com - Update-it-yourself, low cost websites http://www.eatmanifesto.com - against all dumbing down of food Y!:dylan_jay ICQ:520341 MSN:djsq@hotmail.com Ph:+61423198306
--On Freitag, 13. Mai 2005 16:06 Uhr +1000 Dylan Jay <gmane@dylanjay.com> wrote:
When performing a refresh I've read that the cache gets dumped. I've noticed after a refresh the reference counts to objects don't go down. Basically the entire cache seems to be leaked. Is this by design or is it a bug?
hm...is this a big issue since you should never run a production site in debug mode and refresh only works in debug mode? *wink* -aj
I guess its not critical but its unhelpful due to a) Its nicer to users to upgrade products via refresh rather to bounce the server b) Its a pain when debugging memory leaks as you have to restart the server for any code change. I don't know the refresh code but would I be right in saying that a minimise before doing the refresh would be a simple fix? -- Dylan Jay --- http://www.meetmemap.com - makes giving directions easy http://www.pretaweb.com - Update-it-yourself, low cost websites http://www.eatmanifesto.com - against all dumbing down of food Y!:dylan_jay ICQ:520341 MSN:djsq@hotmail.com Ph:+61423198306 "Andreas Jung" <lists@andreas-jung.com> wrote in message news:6E070B5BE67F838D65169854@localhost... --On Freitag, 13. Mai 2005 16:06 Uhr +1000 Dylan Jay <gmane@dylanjay.com> wrote:
When performing a refresh I've read that the cache gets dumped. I've noticed after a refresh the reference counts to objects don't go down. Basically the entire cache seems to be leaked. Is this by design or is it a bug?
hm...is this a big issue since you should never run a production site in debug mode and refresh only works in debug mode? *wink* -aj
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
--On Freitag, 13. Mai 2005 18:02 Uhr +1000 Dylan Jay <gmane@dylanjay.com> wrote:
I guess its not critical but its unhelpful due to a) Its nicer to users to upgrade products via refresh rather to bounce the server
Refresh is a tool thought for development only - but not for upgrading products. Refresh is not a solution for all and everything. So your approach is wrong :-)
b) Its a pain when debugging memory leaks as you have to restart the server for any code change.
Same as above :-) Of course you debug in your testing environment which is a 100% clone of your production server :-) *wink* Andreas
On May 13, 2005, at 10:30, Andreas Jung wrote:
--On Freitag, 13. Mai 2005 18:02 Uhr +1000 Dylan Jay <gmane@dylanjay.com> wrote:
I guess its not critical but its unhelpful due to a) Its nicer to users to upgrade products via refresh rather to bounce the server
Refresh is a tool thought for development only - but not for upgrading products. Refresh is not a solution for all and everything. So your approach is wrong :-)
+1 Refresh works by doing some nasty magic that you really don't want to know about and which has its own problems. Do not take whatever behavior you see with it as some kind of normal production site behavior, that's useless. jens
Andreas Jung wrote at 2005-5-13 08:35 +0200:
... hm...is this a big issue since you should never run a production site in debug mode
Why -- when you can afford the extra time needed for up-to-date checks of file system objects.
and refresh only works in debug mode? *wink*
"refresh" works as well in non-debug mode as in debug mode. -- Dieter
Dylan Jay wrote at 2005-5-13 16:06 +1000:
When performing a refresh I've read that the cache gets dumped. I've noticed after a refresh the reference counts to objects don't go down. Basically the entire cache seems to be leaked.
A well known bug -- said to be fixed in Zope 2.8 (because there the cyclic garbage collector can collect ExtensionClass objects and therefore get rid of the cyclic cache/content structure). It is also easily fixable in earlier Zope versions: In "ZODB.Connection.Connection._resetCache" add "orig_cache.clear()" before "self._cache = cache = PickleCache(...)".
Is this by design or is it a bug?
A bug. -- Dieter
participants (4)
-
Andreas Jung -
Dieter Maurer -
Dylan Jay -
Jens Vagelpohl