Re: [Pyobjc-dev] Memory leak, but only in a plug-in?
Brought to you by:
ronaldoussoren
|
From: Barry W. <bar...@gm...> - 2008-10-12 05:52:30
|
Yes. It'll likely have to wait until I get into work on Monday morning. cheers, Barry On Sat, Oct 11, 2008 at 3:48 PM, Steve Steiner <sst...@ma...> wrote: > Barry, > > Could you please attach the new, improved version of the demo to the > original bug report so any interested party can quickly see the problem. > > Instructions for using Instrument to show the problem might be handy > too if you've got time. > > Thanks, > > S > > On Oct 11, 2008, at 5:17 PM, Barry Wark wrote: > >> On Sat, Oct 11, 2008 at 6:21 AM, Steve Steiner <sst...@ma...> wrote: >>> >>> Hi! >>> >>> Barry Wark and I have been trying to track down a problem in both of >>> our apps. >>> >>> An NSDictionary returned from a plug-in leaks CFDictionary objects >>> in >>> exactly the same number as the number of returned NSDictionary's -- same >>> number of CFDictionary objects, and also allocations for each item in the >>> dictionary flagged as 'keys' and 'object storage.' >> >> Just to clarify the issue: this leak is present if the plugin is >> written in python (and compiled to a loadable bundle using py2app) and >> loaded into an Objective-C app. The leak does not occur if the plugin >> is loaded into a Python app. This issue was first described in bug >> #1982104 >> (http://sourceforge.net/tracker/index.php?func=detail&aid=1982104&group_id=14534&atid=114534). >> >>> >>> This happens regardless of where the dictionary's allocated. >>> Allocating in the main ObjC calling program and passed into the plug-in >>> or >>> created in the plug-in itself, same behaviour. >>> >>> Anybody have a clue why this is? We've proven it pretty >>> conclusively >>> and clearly and have a working demonstration that I can put up if >>> anyone's >>> interested. >>> >>> Thanks, >>> >>> S >>> aka Steve Steiner >>> >>> >>> > > |