New issue
Advanced search Search tips

Issue 799698 link

Starred by 1 user
Status: Verified
Owner: ----
Closed: Jan 2018
Cc:
ifratric@google.com
kkaluri@chromium.org
mac-bugs-priority@chromium.org
dsinclair@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Bus in gldRenderFillPolygonPtr

Project Member Reported by ClusterFuzz, Jan 6 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5426694768033792

Fuzzer: marty_html_twiddler
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Bus
Crash Address: 0x634100020080
Crash State:
  gldRenderFillPolygonPtr
  gleFlushAtomicFunc
  glDrawArrays_IMM_GL3Exec
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=521561:521602

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jan 6 2018

Components: Internals>GPU>Internals
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, Jan 6 2018

Labels: Test-Predator-Auto-Owner
Owner: tsepez@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/a788b14fe2b1e3b94f31c7f20279dee1ebc37353 (Restrict command processed by syscall_broker process.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

Comment 3 by kkaluri@chromium.org, Jan 8 2018

Cc: kkaluri@chromium.org ifratric@google.com
 Issue 799406  has been merged into this issue.

Comment 4 by tsepez@chromium.org, Jan 8 2018

Labels: Test-Predator-Wrong-CLs
Owner: ----
crash is on mac but suspected CL is linux_only.
Project Member

Comment 5 by ClusterFuzz, Jan 30 2018

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

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

Comment 6 by ClusterFuzz, Feb 6 2018

Labels: Needs-Feedback
ClusterFuzz testcase 5426694768033792 is still reproducing on tip-of-tree build (trunk).

Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label.
►

Sign in to add a comment