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

Issue 648132 link

Starred by 1 user
Status: Fixed
Owner:
zmo@chromium.org
Closed: Feb 2017
Cc:
█ manoranj...@chromium.org
█ msrchandra@chromium.org
yunchao...@intel.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Crash in gpu::gles2::RenderbufferAttachment::IsSameAttachment

Project Member Reported by ClusterFuzz, Sep 19 2016 
Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5593947630206976

Fuzzer: afl_gpu_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  gpu::gles2::RenderbufferAttachment::IsSameAttachment
  gpu::gles2::GLES2DecoderImpl::DoBlitFramebufferCHROMIUM
  gpu::gles2::GLES2DecoderImpl::HandleBlitFramebufferCHROMIUM
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=afl_chrome_asan&range=417884:417900

Minimized Testcase (14.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97ffq9wYCIyzjoM1RqUt3xviGXmUUpa6G3fNDt8PdFoDhVEzeTOdEkNi2We7vFHqGFCCxpIH_px5xi2pISNvdG0kkBm8mXqwj_l7FfNHq0GGwZA418QSCYBEwkt2ibz8pwzV9X0PFzhtYV1suze3Du9gb6Wqg?testcase_id=5593947630206976

Issue manually filed by: mmoroz

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

Comment 1 by msrchandra@chromium.org, Nov 3 2016

Cc: msrchandra@chromium.org yunchao...@intel.com
Labels: findit-wrong Test-Predator-Wrong
Findit did not provide any suspect, below is the information,
Suspected CLs	Findit failed to find any stack trace. Is it in a new format?

Assigning to the concern owner fro the CL,
https://chromium.googlesource.com/chromium/src/+log/fe5fb8dd0a77a43120793e60bd20f6d668f1e1c1..36deba9193250475433bdd9a81bff450f87badd8?pretty=fuller

Suspecting Commit# 	faeb732edb9e057db922bc1d623dd0a543b91ca0	
Suspecting Review URL# https://codereview.chromium.org/2329453002

@yunchao.he -- Could you please look into the issue, kindly re-assign if it is not related your change.
Thank You.

Comment 2 by yunchao...@intel.com, Nov 3 2016 

The patch does have issue, but it has been fixed by following patches:
https://codereview.chromium.org/2351093002 (master#420207)
https://codereview.chromium.org/2344273003 (master#419351). 

So, what is the Chromium version? It is not the latest Chromium, right? If its git number is bigger than 420207, I think the crash will not happen. If its git number is between 420207 and 417896, you may catch the crash.

Comment 3 by msrchandra@chromium.org, Nov 3 2016

Cc: manoranj...@chromium.org
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
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

Comment 5 by dtapu...@chromium.org, Jan 31 2017

Components: Internals>GPU

Comment 6 by enne@chromium.org, Jan 31 2017

Owner: zmo@chromium.org
Status: Assigned (was: Untriaged)
zmo, can you take a look at this or find somebody else?

Comment 7 by zmo@chromium.org, Feb 6 2017

Status: Fixed (was: Assigned)
Can no longer reproduce.
►

Sign in to add a comment