I verified that this fixes the WebGL crash in the nested-functions-should-not-crash.html test.
<rdar://problem/17541529>
Created attachment 234491 [details] Patch
Comment on attachment 234491 [details] Patch r=me Is there a performance cost to this limit?
(In reply to comment #3) > (From update of attachment 234491 [details]) > r=me > > Is there a performance cost to this limit? If someone has a shader with more than 256 nested functions, it will no longer compile. I don't think there's a performance hit because this only changes the shader validator, and I think the call depth is counted anyway. It just wasn't used without this change.
Comment on attachment 234491 [details] Patch Clearing flags on attachment: 234491 Committed r170849: <http://trac.webkit.org/changeset/170849>
All reviewed patches have been landed. Closing bug.
Re-opened since this is blocked by bug 134748
this did not break the build and it was not rolled out. reclosing.