New issue
Advanced search Search tips

Issue 919375 link

Starred by 1 user
Status: Fixed
Owner:
clemensh@chromium.org
Closed: Jan 10
Cc:
adamk@chromium.org
titzer@chromium.org
dschuff@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Crash in libappindicator3.so

Project Member Reported by ClusterFuzz, Jan 7 
Detailed report: https://clusterfuzz.com/testcase?key=5922817018953728

Fuzzer: meacer_web_ext
Job Type: linux_asan_chrome_mp
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x6060004b0000
Crash State:
  libappindicator3.so
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mp&range=619628:620208

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
Project Member

Comment 1 by ClusterFuzz, Jan 7

Components: Blink>JavaScript>WebAssembly
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 7

Labels: Test-Predator-Auto-Owner
Owner: clemensh@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/26a78061af924d5277717e07364dcfd20f63d2c3 (Remove trap handler fallback for sanitizers).

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 3 by clemensh@chromium.org, Jan 10

Status: Fixed (was: Assigned)
Fixed by revert: https://crrev.com/c/1396277
Project Member

Comment 4 by ClusterFuzz, Jan 17 (5 days ago)

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

Comment 5 by clemensh@chromium.org, Jan 17 (5 days ago)

Labels: ClusterFuzz-Wrong
Clusterfuzz is still struggling with "bad builds". Setting ClusterFuzz-Wrong to silence these warnings.
►

Sign in to add a comment