Re: Memory leak in eval()'d code

Hi! > I still don't understand *why*, then, the memory stays flat when the new > class does not happen in eval(): Because that code creates only one class. > I checked get_class() for all instances returned, **it's always the same > class name whether it's called from eval() or not**, so this code should > only ever create a single class in memory, right? Why the leak with eval()? There's no leak, eval() just creates new class each time. -- Stas Malyshev smalyshev@gmail.com