Re: CoreAnimation: rendering error 506
Re: CoreAnimation: rendering error 506
- Subject: Re: CoreAnimation: rendering error 506
- From: David Duncan <email@hidden>
- Date: Sun, 24 Mar 2013 14:20:57 -0700
On Mar 24, 2013, at 2:14 PM, Oleg Krupnov <email@hidden> wrote:
> All right, then what is "Invalid Framebuffer"? What kind of (mis)use of Core Animation *might* produce this error? Too large layers? Zero sized layers? Some combination of layer properties?
Invalid framebuffer basically means that a something tried to set an invalid framebuffer ID as current in GL. Unfortunately it doesn't really say a whole lot other than "debug to make sure all your framebuffer IDs are valid".
> I've made some experiments trying to isolate the problem, and it seems that it happens to layers whose content is drawn via delegate, namely after calling setNeedsDisplay on a layer, if its delegate implements drawLayer:inContext:, even if this method is empty. If I comment out that method entirely, i.e. make it non-implemented, the problem disappears. Does it ring something?
Alas no, but it would be useful information to put in the bug report.
(I'm not familiar enough to know why the implementation would trigger this, I was just aware of what this message meant due to other reasons).
>
>
> On Mar 24, 2013, at 10:58 PM, David Duncan <email@hidden> wrote:
>
>> On Mar 24, 2013, at 1:17 PM, Oleg Krupnov <email@hidden> wrote:
>>
>>> No, only Core Animation with simple CALayers.
>>>
>>> Can it be indicative of some problems in my code, or should I just ignore it? Everything seems to work fine otherwise. The messages are quite annoying though. Besides, it seems that in previous version of my app the messages did not appear, or maybe I did not notice them. It's now hard to tell what change caused them to appear - there have been too many changes since that time. Maybe it's even some changes in the OS, it's hard to tell.
>>
>> I'm not certain, but if you can reproduce it consistently I would file a bug.
>>
>>> Is there a way to put a breakpoint or otherwise track the cause of the problem?
>>
>> I don't think so. The problem is that the error happened a fair amount of time before the error is actually reported, so the only information available is that an error occurred, not where it happened.
>>
>>>
>>> On Mar 24, 2013, at 9:59 PM, David Duncan <email@hidden> wrote:
>>>
>>>> On Mar 23, 2013, at 5:00 AM, Oleg Krupnov <email@hidden> 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 OpenGL or a CAOpenGLLayer?
>>>> --
>>>> David Duncan
>>>>
>>
>> --
>> David Duncan
>>
--
David Duncan
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden