Weird memory consumption problem.

[Bo Peng]

Steven D'Aprano wrote:

> Sorry, are you saying that the code you posted does NOT have a memory 
> leak, but you want us to find the memory leak in your real code sight 
> unseen?

valgrind does not detect anything so it does not look like memory leak. 
I just can not figure out why val[0], readonly access to a tuple 
element, can cause this kind of problem.

Anyway, is there a way to list all or newly added python objects? I 
guess I can trace the ref_cnt of the tuple element manually.

Bo