Breakpoint in blink::FontCache::CrashWithFontInfo |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4915198847352832 Fuzzer: inferno_webbot Job Type: windows_asan_chrome_with_gpu Platform Id: windows Crash Type: Breakpoint Crash Address: 0x000000000000 Crash State: v8::internal::Snapshot::DefaultSnapshotBlob Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4915198847352832 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jul 18
Seems like the stack trace of the reproduced crash is garbage. The original run crashed in blink::FontCache::CrashWithFontInfo, which is not v8 related.
,
Jul 19
,
Jul 19
See comment 2. If you think this is v8-related, please elaborate.
,
Jul 24
ClusterFuzz has detected this issue as fixed in range 577436:577437. Detailed report: https://clusterfuzz.com/testcase?key=4915198847352832 Fuzzer: inferno_webbot Job Type: windows_asan_chrome_with_gpu Platform Id: windows Crash Type: Breakpoint Crash Address: 0x000000000000 Crash State: v8::internal::Snapshot::DefaultSnapshotBlob Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=570766:570768 Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=577436:577437 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4915198847352832 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 24
ClusterFuzz testcase 4915198847352832 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 kkaluri@chromium.org
, Jul 16