New issue
Advanced search Search tips

Issue 895078 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Dec 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in validate_edge_pair

Project Member Reported by ClusterFuzz, Oct 13

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=6020194668118016

Fuzzer: inferno_canvas_wrecker
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000001
Crash State:
  validate_edge_pair
  validate_edge_pair
  validate_edge_list
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=572049:572050

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Oct 13

Components: 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.
Project Member

Comment 2 by ClusterFuzz, Oct 13

Labels: Test-Predator-Auto-Owner
Owner: senorblanco@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://skia.googlesource.com/skia/+/24289e05d55ccdc04ef239c7972d2b52e402ad0f (GrTessellator: handle three consecutive collinear edges.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Cc: davidqu@chromium.org senorblanco@chromium.org
 Issue 864928  has been merged into this issue.
Project Member

Comment 4 by ClusterFuzz, Dec 10

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

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

Comment 5 by ClusterFuzz, Dec 17

Labels: Needs-Feedback
ClusterFuzz testcase 6020194668118016 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