-
I'm attaching a zip'd project directory demonstrating the memory leak for NSDictionary instances passed from a python plugin (built with py2app) back to an Objective-C loader.
The included demo.trace Instruments document contains a UI script that will replicate the behavior. Adding an "Object Alloc" instrument will show that instances of CFDictionary and CFString are created but not released...
2008-10-14 01:01:31 UTC in PyObjC
-
A little bit of extra information:
gc.garbage is empty ([]) after calling gc.set_debug(gc.DEBUG_LEAKS) and gc.collect() does not resolve the memory leak (no system memory is returned).
2008-06-13 01:35:10 UTC in PyObjC
-
For some reason, I'm unable to attach the zip file, so it's available at http://rieke-server.physiol.washington.edu/~barry/python/PyObjCTest.zip.
2008-06-02 13:26:50 UTC in PyObjC
-
I have an Objective-C application that uses plugins to generate some
data. THe app is compiled against the 10.5 SDK and is running on
Leopard (with the system python and pyobjc). The data is returned as
NSData instances and its parameters as an NSDictionary instance, as
defined by the app's plugin formal protocol. Some of our plugins are
written in Objective-C and some in Python ("compiled"...
2008-06-02 13:19:40 UTC in PyObjC
-
Between py2app 0.3.2 and 0.3.4, building plugins that load broke. I've
included a demo of the problem as an Xcode project. Building and
running the command line tool target will build the plugin as well.
The command line tool simply attempts to load the plugin. (you may
have to copy the built plugin bundle to the products directory or
change the path to the plugin in the project's products...
2006-10-04 16:23:56 UTC in PyObjC
