New issue
Advanced search Search tips

Issue 816395 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2018
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in gdk_cairo_surface_paint_pixbuf

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

Fuzzer: cdiehl_peach
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900007fbd
Crash State:
  gdk_cairo_surface_paint_pixbuf
  gdk_cairo_surface_create_from_pixbuf
  gtk_drag_get_cursor
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=539053:539054

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

Additional requirements: Requires Gestures

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Feb 26 2018

Labels: Test-Predator-Auto-Owner
Owner: dominickn@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/0b679185592fd608a2a5e422b3e89362e6f518fe (Clarify in the console message that permissions embargo can be cleared.).

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.

Comment 2 by dominickn@chromium.org, Feb 26 2018

Labels: Test-Predator-Wrong-CLs
Owner: ----
Status: Unconfirmed (was: Assigned)
Looks like a crash in gtk. My CL changes strings that are printed to the JavaScript console, so I highly doubt it's the cause of a gtk crash.
Project Member

Comment 3 by ClusterFuzz, Mar 12 2018

Status: WontFix (was: Unconfirmed)
ClusterFuzz testcase 5651036329738240 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