typeface. Could not find any font: ADDRESS, sans in platform_font_linux.cc |
|||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5252924272017408 Fuzzer: meacer_extension_apis Job Type: linux_ubsan_vptr_chrome Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: typeface. Could not find any font: ADDRESS, sans in platform_font_linux.cc gfx::CreateSkTypeface gfx::PlatformFontLinux::PlatformFontLinux Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_vptr_chrome&range=370165:370699 Minimized Testcase (7.99 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97dpg41YrjEEdBd0O7rzf8qX8F60__a1P4wzfCU30y6Zzp5Jwz8uwL7gr16l8RUklAcHN025gllFQEORpq63nIzXDa0ffmRvNYbluSRSYGAGK9XbKzq4Szp3YmlRXatoGQHvwzndtxuNw-zEEGwF7Fj5FZlHA?testcase_id=5252924272017408 Filer: kavvaru See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jul 12 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 12 2016
My CL is completely unrelated. Route to Fonts triage.
,
Jul 12 2016
The failure is in the Chrome font code, not in Blink.
,
Oct 18 2016
,
Oct 20 2016
ClusterFuzz has detected this issue as fixed in range 419561:419601. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5252924272017408 Fuzzer: meacer_extension_apis Job Type: linux_ubsan_vptr_chrome Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: typeface. Could not find any font: ADDRESS, sans in platform_font_linux.cc gfx::CreateSkTypeface gfx::PlatformFontLinux::PlatformFontLinux Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_vptr_chrome&range=370165:370699 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_vptr_chrome&range=419561:419601 Minimized Testcase (7.99 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97dpg41YrjEEdBd0O7rzf8qX8F60__a1P4wzfCU30y6Zzp5Jwz8uwL7gr16l8RUklAcHN025gllFQEORpq63nIzXDa0ffmRvNYbluSRSYGAGK9XbKzq4Szp3YmlRXatoGQHvwzndtxuNw-zEEGwF7Fj5FZlHA?testcase_id=5252924272017408 See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Oct 20 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by kavvaru@chromium.org
, Jul 12 2016Labels: Te-Logged M-53
Owner: tkent@chromium.org
Status: Assigned (was: Available)