I think you have to provide the test program for others to help you,
or you can debug by yourself,

http://docs.python.org/library/gc.html
"To debug a leaking program call gc.set_debug(gc.DEBUG_LEAK)."

On Jun 12, 1:02 am, Димка Платон <[email protected]> wrote:
> Now i am sure that memory problems connected with pylons itself not
> sqlalchemy. After testing i saw that memory for using query results was
> free. But it development and production mode it still grows when template
> generating. It feels that problem connect with response memory. Any ideas?

-- 
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.

Reply via email to