On 07/09/2012 05:14 AM, Rémi Chaintreuil wrote:
Le vendredi 6 juillet 2012 15:28:09 UTC+2, Chris McDonough a écrit :Be sure you're not using the Pyramid debugtoolbar in this configuration. - C Thanks for your response. I already removed the debugtoolbar. I've tried other templates engines (Jinja2 and Mako), but the increase of memory use remains. I also forgot to add xhr.close in my Javascript, but it doesn't solve the problem either. Is Pyramid caching the responses the same way the compiled templates are cached in memory, and clearing this cache only on deployment ?
No. In this
case, how can I prevent this behaviour ?
It doesn't do that. - C
-- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/fRQkg6hUnTAJ. 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/pylons-discuss?hl=en.
-- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
