New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 813316 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
hcm@chromium.org
█ caryclark@google.com
reed@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in base::OnNoMemorySize

Project Member Reported by ClusterFuzz, Feb 17 2018 
Detailed report: https://clusterfuzz.com/testcase?key=4755322577879040

Fuzzer: libFuzzer_skia_image_filter_proto_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e90000238a
Crash State:
  base::OnNoMemorySize
  SkAutoSTArray<32, float>::reset
  SkDashImpl::CreateProc
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=534732:534740

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Feb 17 2018

Components: Internals>Core 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.

Comment 2 by hcm@chromium.org, Apr 9 2018

Cc: caryclark@google.com reed@google.com

Comment 3 by hcm@chromium.org, Apr 9 2018

Status: Available (was: Untriaged)

Comment 4 by caryclark@google.com, Apr 9 2018

Cc: hcm@chromium.org
Status: WontFix (was: Available)
My understanding is that if Skia runs out of space, it crashes by design. Is that not the case here, or is that behavior no longer acceptable?
Project Member

Comment 5 by ClusterFuzz, Apr 16 2018

Labels: Needs-Feedback
ClusterFuzz testcase 4755322577879040 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.
►

Sign in to add a comment