Automatically applying components based on crash stacktrace and information from OWNERS files.
If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Yes, it's probably related and I'm planning to roll in a new version of libxml today to address these issues. This time I'll add tests too, since nothing failed on the waterfall when I reverted the other version.
ClusterFuzz testcase 4731710961614848 is verified as fixed, so closing issue as verified.
If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
This bug requires manual review: M66 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), josafat@(ChromeOS), abdulsyed@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Sheriff Bot aded the merge request based on labels. The actual merge request from me is on https://bugs.chromium.org/p/chromium/issues/detail?id=793715
Regardless, as far as we know so far it's safe. It fixes the security issues and to my knowledge doesn't add any new issues. It's basically the version that was present in M-65, 66 and 67 until I reverted it, with a fix for the issues that caused the revert.
Comment 1 by ClusterFuzz
, Mar 19 2018