Reference leaks in trunk

[GoogleCodeExporter]

Since the change to automatically compile hot functions with LLVM, Python's
refleak tests fail because the JIT compilation creates a new
_llvmfunctionobject Python object.

Approaches to fixing this:
- Don't allocate a new Python object to hold the pointer to the
llvm::Function. This would require a getter to create the Python object
when the user looked up the co_llvm attribute. (My preference)
- Disable JITting during refleak iterations.

Original issue reported on code.google.com by collinw on 8 Jun 2009 at 5:59

[GoogleCodeExporter]

Patch mailed out for review.

Original comment by collinw on 12 Jun 2009 at 10:13

• Changed state: Started

[GoogleCodeExporter]

Fixed in r638.

Original comment by collinw on 13 Jun 2009 at 12:21

• Changed state: Fixed