Issue metadata
Sign in to add a comment
|
Breakpoint in blink::FontCache::CrashWithFontInfo |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6607598514864128 Fuzzer: jsbell_serviceworker Job Type: windows_asan_chrome_no_sandbox Platform Id: windows Crash Type: Breakpoint Crash Address: 0xffff9d06758f4080 Crash State: blink::FontCache::CrashWithFontInfo blink::HarfBuzzShaper::ShapeSegment blink::HarfBuzzShaper::Shape Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6607598514864128 Additional requirements: Requires Gestures Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jun 10 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Jun 10 2018
,
Jun 10 2018
,
Jun 11 2018
Anyone want to pick this one up?
,
Jun 12 2018
this doesn't look like a security bug, it's crashing failing to get a fallback font. it's a crash we also see in the wild. It looks flaky on clusterfuzz as well...
,
Sep 19
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Jun 10 2018