CHECK failure: count <= MaxElementCountInBackingStore<T>() in partition_allocator.h |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5218406190809088 Fuzzer: ifratric-browserfuzzer-v3 Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: CHECK failure Crash Address: Crash State: count <= MaxElementCountInBackingStore<T>() in partition_allocator.h blink::GraphemesClusterList blink::HarfBuzzShaper::CommitGlyphs Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=575495:575496 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5218406190809088 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jul 19
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/1e3235b397f5fd7e875ae1548ee2ce385cb22af8 (Add support for mid ligature positions). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Jul 28
ClusterFuzz has detected this issue as fixed in range 578698:578699. Detailed report: https://clusterfuzz.com/testcase?key=5218406190809088 Fuzzer: ifratric-browserfuzzer-v3 Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: CHECK failure Crash Address: Crash State: count <= MaxElementCountInBackingStore<T>() in partition_allocator.h blink::GraphemesClusterList blink::HarfBuzzShaper::CommitGlyphs Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=575495:575496 Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_no_sandbox&range=578698:578699 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5218406190809088 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jul 28
ClusterFuzz testcase 5218406190809088 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Jul 19