New issue
Advanced search Search tips

Issue 842483 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in sk_abort_no_print

Project Member Reported by ClusterFuzz, May 13 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5038689596735488

Fuzzer: libFuzzer_skia_color_space_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0539000036ee
Crash State:
  sk_abort_no_print
  get_skcms_format
  SkColorSpaceXform_skcms::apply
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=552556:552566

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5038689596735488

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, May 13 2018

Components: Internals>Skia
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, May 13 2018

Cc: noel@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 3 by ClusterFuzz, May 13 2018

Cc: brianosman@google.com
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Enable skcms in Skia by brianosman@google.com - https://chromium.googlesource.com/chromium/src/+/a3796c2471b11c81c8b532d66388c1b5ea708c07

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
Project Member

Comment 4 by bugdroid1@chromium.org, May 14 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0d60e31c320349d7078a87754ce54a0edbbd485f

commit 0d60e31c320349d7078a87754ce54a0edbbd485f
Author: Brian Osman <brianosman@google.com>
Date: Mon May 14 17:19:31 2018

Limit color space xform formats to the valid range in fuzzing

There are only 7 ColorFormat values.

Bug:  chromium:842483 
Change-Id: I92e10ed9147b8df607fd5ea62e9a0a5f2300c14c
Reviewed-on: https://chromium-review.googlesource.com/1057452
Reviewed-by: Mike Klein <mtklein@google.com>
Reviewed-by: Mike Klein <mtklein@chromium.org>
Reviewed-by: Jonathan Metzman <metzman@chromium.org>
Commit-Queue: Brian Osman <brianosman@google.com>
Cr-Commit-Position: refs/heads/master@{#558351}
[modify] https://crrev.com/0d60e31c320349d7078a87754ce54a0edbbd485f/testing/libfuzzer/fuzzers/skia_color_space_fuzzer.cc

Project Member

Comment 5 by ClusterFuzz, May 15 2018

ClusterFuzz has detected this issue as fixed in range 558350:558376.

Detailed report: https://clusterfuzz.com/testcase?key=5038689596735488

Fuzzer: libFuzzer_skia_color_space_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0539000036ee
Crash State:
  sk_abort_no_print
  get_skcms_format
  SkColorSpaceXform_skcms::apply
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=552556:552566
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=558350:558376

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5038689596735488

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.
Project Member

Comment 6 by ClusterFuzz, May 15 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 5038689596735488 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