Abrt in sk_abort_no_print |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5117042746458112 Fuzzer: libFuzzer_skia_color_space_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Abrt Crash Address: 0x03e900004724 Crash State: sk_abort_no_print SkColorSpace_XYZ::fromXYZD50 void SkOnce::operator Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=463054:463440 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5117042746458112 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Jul 11 2017
,
Jul 11 2017
This is a debug-only assertion triggered when we're asked to invert a non-invertible colorspace gamut matrix. We don't crash or explicitly fail in this case except in debug mode (instead we give back sRGB's inverse... not entirely sure why).
,
Jul 15 2017
> (instead we give back sRGB's inverse... not entirely sure why). Skia color space handling of bogus profiles is like an eager-to-please puppy: it just wants to give you a color profile. It's run home to mama (sRGB) approach is gonna cause compat problems long-term, I expect. ColorSync on OSX would not accept this profile and declare it bogus. Skia seems not to do that, and instead gives you (or assumes) sRGB, instead to declaring the profile bogus.
,
Jul 15 2017
https://bugs.chromium.org/p/chromium/issues/detail?id=734354 also needs fixing.
,
Jul 15 2017
Issue 734354 has been merged into this issue.
,
Jul 19 2017
ClusterFuzz testcase 5117042746458112 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
,
Jul 19 2017
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Nov 7 2017
,
Dec 20 2017
ClusterFuzz has detected this issue as fixed in range 525188:525211. Detailed report: https://clusterfuzz.com/testcase?key=5117042746458112 Fuzzer: libFuzzer_skia_color_space_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Abrt Crash Address: 0x03e900004724 Crash State: sk_abort_no_print SkColorSpace_XYZ::fromXYZD50 void SkOnce::operator Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=463054:463440 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=525188:525211 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5117042746458112 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by msrchandra@chromium.org
, Jun 19 2017Labels: Test-Predator-Wrong-CLs M-61