You could do a bisect on the source code and find the commit that introduced the bug. You might be able to find a flaw in the code pretty quickly and submit a patch with your report. It also helps to be active on #chromium on Freenode. People will look at your bug if you are active in there.
Thanks, I have updated the blog post accordingly. There is a conspicuous note at the top now saying the problem will be fixed in version 38. I think the blog post still makes sense, as it will be a while for the fix to become effective for everybody.
But this is more likely to be a result of one of the underlying repositories. For instance, it looks like Blink was rolled back from 091cb19dc52917020bfda19b2a41d8f097c02d92 to 6894b21e75041bc3e050a7591388f866cbe7282b.
Thank you for reporting this level of detail; having a narrow revision range is helpful for tracking down bugs.
12 comments
[ 3.2 ms ] story [ 38.2 ms ] threadhttps://code.google.com/p/chromium/issues/detail?id=412640
It was responded to immediately, tracked down, and fixed in M38.
I don't have beta installed, but I can confirm it's fixed in dev channel and Canary (Chrome 39).
https://code.google.com/p/chromium/issues/detail?id=418268
It's interesting that it happens in .124 but not .122. Does anyone know if it's possible to see the list of changes between those releases?
The changes to Chromium itself are here: https://chromium.googlesource.com/chromium/src/+log/37.0.206...
But this is more likely to be a result of one of the underlying repositories. For instance, it looks like Blink was rolled back from 091cb19dc52917020bfda19b2a41d8f097c02d92 to 6894b21e75041bc3e050a7591388f866cbe7282b.
Thank you for reporting this level of detail; having a narrow revision range is helpful for tracking down bugs.
I'll probably need to add this one to the list!