Re: How to find EXC_BAD_ACCESS bug?

FROM : Sean McBride
DATE : Sun Aug 29 21:47:54 2004

Steve Sims (<email_removed>) on Sat, Aug 28, 2004 18:27 said:

>Eventually I did the last thing you suggest, and ripped out code.  The
>first thing I removed was a call within my display routine that
>incrementally added a clipping bezier to the current graphics context. 
>As if by magic the exception disappeared.


You ripped things out in the right order. :)

>It would seem therefore that there may be a limitation within Quartz as
>to the number of clipping paths you can add to a context, and that if
>you exceed this limit you'll get memory corruption.  I'm not sure
>exactly how many clipping paths there were, but I'd guess I had
>typically added about 20 when the crash occurred.  It is, however, not
>entirely consistent and may also be related to free memory - I don't
>have much RAM.


You could check with the quartz list:
<http://lists.apple.com/mailman/listinfo/quartz-dev>

Maybe you have found an OS bug that Apple would like to know about...
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.