To get the leak the __del__method has to be in the class. The gc.collect() as suggested by Massimo cured the leak for the exec code case I believe because gc.collect() runs a test on the objects to see if there are any external references, finds none, and therefore allows them to be removed from the heap.
- [web2py] Re: on a possible web2py memory leak Anthony
- [web2py] Re: on a possible web2py memory leak Massimo Di Pierro
- [web2py] Re: on a possible web2py memory leak ron_m
- [web2py] Re: on a possible web2py memory leak ron_m
- [web2py] Re: on a possible web2py memory leak VP
- [web2py] Re: on a possible web2py memory leak ron_m
- [web2py] Re: on a possible web2py memory leak Massimo Di Pierro
- [web2py] Re: on a possible web2py memory leak Anthony
- [web2py] Re: on a possible web2py memory le... ron_m
- [web2py] Re: on a possible web2py memory le... ron_m
- [web2py] Re: on a possible web2py memor... Anthony
- [web2py] Re: on a possible web2py ... Massimo Di Pierro
- Re: [web2py] Re: on a possible... Jonathan Lundell
- [web2py] Re: on a possible web... Massimo Di Pierro
- [web2py] Re: on a possible web... ron_m
- Re: [web2py] Re: on a possible... Michele Comitini
- [web2py] Re: on a possible web... Massimo Di Pierro
- Re: [web2py] Re: on a possible web2py memory le... Jonathan Lundell
- [web2py] Re: on a possible web2py memory le... Massimo Di Pierro
- [web2py] Re: on a possible web2py memory leak ron_m

