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

Issue 816754 link

Starred by 1 user
Status: WontFix
Owner:
schenney@chromium.org
Closed: Mar 2018
Cc:
█ brajkumar@chromium.org
█ mbarowsky+blinkimage@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression



Sign in to add a comment

BUS error with ubsan ImageFrameGenerator.cpp

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

Fuzzer: inferno_webbot
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: Bus
Crash Address: 0x7fb00ed1c000
Crash State:
  NULL
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=539260:539265

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
Project Member

Comment 1 by ClusterFuzz, Feb 27 2018

Components: Blink>Paint
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 brajkumar@chromium.org, Feb 27 2018

Cc: brajkumar@chromium.org
Labels: -Type-Bug M-66 Test-Predator-Wrong Type-Bug-Regression
Unable to find actual suspect through code search nor from the provided regression range, hence adding appropriate label for further triage.

Thanks!

Comment 3 by brajkumar@chromium.org, Feb 27 2018

Labels: CF-NeedsTriage

Comment 4 by schenney@chromium.org, Feb 27 2018

Components: -Blink>Paint Internals>Network

Comment 5 by schenney@chromium.org, Feb 27 2018

Components: -Internals>Network Blink>Image
Owner: schenney@chromium.org
Status: Assigned (was: Untriaged)
Summary: BUS error with ubsan ImageFrameGenerator.cpp

Comment 6 by schenney@chromium.org, Feb 27 2018 

As usual, regression range seems wrong.
Project Member

Comment 7 by ClusterFuzz, Mar 13 2018

Status: WontFix (was: Assigned)
ClusterFuzz testcase 4865649852284928 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
►

Sign in to add a comment