:59 PM, David Duncan david.dun...@apple.com wrote:
On Mar 23, 2013, at 5:00 AM, Oleg Krupnov oleg.krup...@gmail.com wrote:
I get many repetitive messages in the console: CoreAnimation: rendering
error 506
This is a GL error, in this case Invalid Framebuffer.
Does your application use
is
that an error occurred, not where it happened.
On Mar 24, 2013, at 9:59 PM, David Duncan david.dun...@apple.com wrote:
On Mar 23, 2013, at 5:00 AM, Oleg Krupnov oleg.krup...@gmail.com wrote:
I get many repetitive messages in the console: CoreAnimation: rendering
error 506
This is a GL
in the console: CoreAnimation: rendering
error 506
This is a GL error, in this case Invalid Framebuffer.
Does your application use OpenGL or a CAOpenGLLayer?
--
David Duncan
--
David Duncan
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com
is that an error occurred, not where it happened.
On Mar 24, 2013, at 9:59 PM, David Duncan david.dun...@apple.com wrote:
On Mar 23, 2013, at 5:00 AM, Oleg Krupnov oleg.krup...@gmail.com wrote:
I get many repetitive messages in the console: CoreAnimation: rendering
error 506
This is a GL error
On 25/03/2013, at 8:14 AM, Oleg Krupnov oleg.krup...@gmail.com wrote:
All right, then what is Invalid Framebuffer? What kind of (mis)use of Core
Animation *might* produce this error? Too large layers?
I think I've seen this error when using CAShapeLayer and the frame size
exceeded a
I get many repetitive messages in the console: CoreAnimation:
rendering error 506
It disappears when I turn off creating any child layers in my
layer-hosting views.
What could it be caused by?
Can I somehow insert a breakpoint to catch where this output is made?
I tried symbolic breakpoints
