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

Issue 662952 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Nov 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Crash in findX

Project Member Reported by ClusterFuzz, Nov 7 2016

Issue description

Components: Internals>Skia
Labels: Test-Predator-Wrong-CLs M-56 Te-Logged
Owner: liyuqian@chromium.org
Status: Assigned (was: Untriaged)
Author: liyuqian
Project: chromium-skia
Changelist: https://skia.googlesource.com/skia.git/+/2add0ffdaab4c33ca6702c81533c88c7b5ca7294
Time: Thu Oct 20 11:04:39 2016 -0700
The CL last changed line 1323 of file SkScan_AAAPath.cpp, which is stack frame 4.

liyuqian@, could you please take a look and reassign if it is not related your changes.
Thank you
Project Member

Comment 2 by ClusterFuzz, Nov 8 2016

ClusterFuzz has detected this issue as fixed in range 430262:430287.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5662128553066496

Fuzzer: bj_broddelwerk
Job Type: linux_lsan_chrome_mp
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000000
Crash State:
  findX
  SkAAClipBlitter::blitV
  aaa_walk_convex_edges
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=430188:430192
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_lsan_chrome_mp&range=430262:430287

Minimized Testcase (0.37 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97xNbBofjYWm02kouSSW6FbhM6ZufM1tMYwHFb88xhDfgy79GTFeirwlQgwSm6hc-NcUHIpevFQuJeBRLfP8l5LWPNS8FCEy5H-28nCpde4MAJVvew1WqOW1Afp1FOxaKY2ddRXKoVSv3-iHmHnZsNzg--r8w?testcase_id=5662128553066496

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 3 by ClusterFuzz, Nov 8 2016

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase is verified as fixed, closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
The following CL should fix it.

https://codereview.chromium.org/2481703004/
Status: Started (was: Verified)
Status: Assigned (was: Started)
Status: Started (was: Assigned)
Please ignore the CL posted above (https://codereview.chromium.org/2481703004/). That CL is for chromium:662925 (this is chromium:662952; moreover, both these bugs have a final fail in findX, which are really confusing).

The actual CL that fixes this is: https://codereview.chromium.org/2485243002/
Status: Fixed (was: Started)
Project Member

Comment 10 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

Sign in to add a comment