On 22/07/2009, at 2:42 AM, Nick Zitzmann wrote:
One thought: Are you using the -CGImage method of NSBitmapImageRep
anywhere? If so, then you absolutely must not deallocate the
NSBitmapImageRep while the CGImageRef is live, because the
CGImageRef acquired via -CGImage is still using the
N
First of all, thanks a lot for all the effort! Seems my original
message was to long, so here is the shortened version:
There is also considerable "artifacting" during column drags and
resizing operations (also unaffected cells are often not redrawn
correctly after resizing, leading me to
It's not intended to be an accurate statement. The point is to avoid
jumping to conclusions. Framework code is far more exposed than your
own, and it is immensely more likely that you've screwed up than the
Quartz devs have.
I get that. I just don't think that's necessarily a good place to
On Tue, Jul 21, 2009 at 9:56 AM, I. Savant wrote:
> That's just not true. Plenty of bugs in the frameworks. I've
> personally logged dozens. It's USUALLY your code but certainly not
> always.
It's not intended to be an accurate statement. The point is to avoid
jumping to conclusions. Framework
On Tuesday, July 21, 2009, Kyle Sluder wrote:
> Remember, 90% of the time, the bug is in your code. The other 10% of
> the time, the bug is in your code.
That's just not true. Plenty of bugs in the frameworks. I've
personally logged dozens. It's USUALLY your code but certainly not
always.
On Jul 21, 2009, at 10:32 AM, 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 unintentiona
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 unintentional
On Tue, Jul 21, 2009 at 9:32 AM, Tim Schmidt wrote:
> Obviously CG's bitblock transfers access unallocated memory in this case.
No, it probably doesn't.
Remember, 90% of the time, the bug is in your code. The other 10% of
the time, the bug is in your code.
> If
> I accidently free said memory i
On Jul 20, 2009, at 11:18 PM, Alexander Spohr wrote:
Am 21.07.2009 um 00:38 schrieb Tim Schmidt:
Is there any way to work around this
Yes: find your memory bug.
EXC_BAD_ACCESS almost always is a memory bug in your code.
atze
Obviously CG's bitblock transfers access unallocated
Am 21.07.2009 um 00:38 schrieb Tim Schmidt:
Is there any way to work around this
Yes: find your memory bug.
EXC_BAD_ACCESS almost always is a memory bug in your code.
atze
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do
10 matches
Mail list logo
