> I've tried to get small examples that show the bugs, and failed.
Have you tried setting up an automated process which tries to gradually reduce your large codebase to a small one which still reproduces the bug?
Some similar existing projects: Tigris Delta for C/C++ code, Bugpoint for LLVM, and my own DustMite (https://github.com/CyberShadow/DustMite) for D code. I wonder if something like that already exists for HTML.
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...
Have you tried setting up an automated process which tries to gradually reduce your large codebase to a small one which still reproduces the bug?
Some similar existing projects: Tigris Delta for C/C++ code, Bugpoint for LLVM, and my own DustMite (https://github.com/CyberShadow/DustMite) for D code. I wonder if something like that already exists for HTML.