New issue
Advanced search Search tips

Issue 706373 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: Mar 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Crash in SignalAction

Project Member Reported by ClusterFuzz, Mar 29 2017

Issue description

Labels: Test-Predator-Wrong M-59
Owner: dmu...@chromium.org
Status: Assigned (was: Untriaged)
Through regression range, suspected CL is 
https://chromium.googlesource.com/chromium/src/+/ec764054b12a8e21e1fe958c3f1e4d47df671066
Looks like dupe of  issue 705837 . dmurph@, could you please take a look and duplicate if both are same root cause?.
Thank you.
Project Member

Comment 2 by ClusterFuzz, Mar 30 2017

ClusterFuzz has detected this issue as fixed in range 460522:460544.

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

Fuzzer: therealholden_worker
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x000000000000
Crash State:
  SignalAction
  content::LevelDBIteratorImpl::IsValid
  content::LevelDBTransaction::TransactionIterator::HandleConflictsAndDeletes
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=459923:459938
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=460522:460544

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94_qgp-LrPrIEwc3uyk6wckgmAQUhMF188c-iKP87BMB3asuAkCviWhBmDYoT5GMAxxK9PmW9MeKgKhT2kQTJwPuQ5RgL2aOiGddKjcs_lQUVzQuRLW1PQf997muhKMST0eHvDlAcLBifChazaAHaxDG6Rzk6Nz20VUtxLnZRmoby01zzXtWczDQuf3e2wfyr0rCXyc2WZXxQfF9jkD0vArTo_8L0yXmD-I1beYaAZlFDYtnryJDSYEqEyeuY5ZW-0MeGgaJspV6WE3XjORqKgiq9McwSNbt5uqrojFvAk4zyHgzoJVXNbx5nqlb-T5kwXJMfc4_X7foI3Ky4-cUmyjsTI6uAQqc7KF5YzSHMsn3Jo_JK1Vf5gATKy8pP_U7taQ0rDYGGmi7MeIVyvs4lMv-PAPqg?testcase_id=5181997980057600


Additional requirements: Requires HTTP

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, Mar 30 2017

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

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

Sign in to add a comment