On Jul 21, 2009, at 12:32 PM, Tim Schmidt wrote:
Obviously CG's bitblock transfers access unallocated memory in this case. If I accidently free said memory it completely eludes me where this might happen (I am pretty confident I don't release any of my model/controller objects unintentionally (I tried running with all the usual mallocdebug options as well as NSZombies). Furthermore all NIBs are managed by NSViewController subclasses. Can anybody point me to some advanced guides on NSTableView (beyond the class reference and tables guide).
I'll assume you're not customizing the drag and drop process (or doing anything with the column drag delegate method).
My own intuition tells me you might look into your cells. If you have any custom (header or data) cells for the column(s) involved or do any custom manipulation of those cells (such as with ...willDisplayCell:...) that'd be a place to start looking for memory management no-nos. Especially if it only happens with particular columns.
Also, if you're using the table datasource protocol, it's possible your ...objectValue... datasource method is returning an improperly- managed instance of something or other.
If you're doing anything custom, post your code. -- I.S. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
