22 Dec
2008
22 Dec
'08
9:11 p.m.
If that code is the real problem (in a reproducible test case), then this approach is the only acceptable solution. Disabling long-running code is not acceptable.
By "disabling", I meant disabling the optimization that's trying to rearrange the arenas so that more memory can be returned to the OS.
I meant the same thing - I'm opposed to giving up one feature or optimization in favor of a different feature or optimization.
This presumably wouldn't be any worse than things were in Python 2.4, when memory was never returned to the OS.
Going back to the state of Python 2.4 would not be acceptable. Regards, Martin