Re:Tragedy of the WebKit Commons
by erichocean on Thursday February 14, 2013 @11:09AM
(#5220060)
I haven't, although I'm sure with enough effort, I could build a one-off tool to figure out what exactly the problem is.
If I was developing Chrome's compositor, sure, I'd do that.
One difficulty is that the "bad" code is actually generated HTML and CSS. Well, the generated code is fine, it's the browser that eventually has problems with it, but you get what I mean.
There's probably a way to capture that output in buffers over multiple event loops, and then do something like Bugpoint over that output and see if I can't reproduce/reduce the issue.
I'm also not sure if the Canvas drawing I'm doing is part of the issue or not, so I'd probably have to capture that as well...
If I was developing Chrome's compositor, sure, I'd do that.
One difficulty is that the "bad" code is actually generated HTML and CSS. Well, the generated code is fine, it's the browser that eventually has problems with it, but you get what I mean.
There's probably a way to capture that output in buffers over multiple event loops, and then do something like Bugpoint over that output and see if I can't reproduce/reduce the issue.
I'm also not sure if the Canvas drawing I'm doing is part of the issue or not, so I'd probably have to capture that as well...