New issue
Advanced search Search tips

Issue 702373 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

process_ > 0 in process_posix.cc

Project Member Reported by ClusterFuzz, Mar 16 2017

Issue description

Labels: M57 Test-Predator-Wrong
Owner: haraken@chromium.org
Status: Assigned (was: Untriaged)
Through code search on file process_posix.cc, suspected CL is
https://chromium.googlesource.com/chromium/src/+/940efb95e8eb38337c4df327792b71dcc2de2d84
haraken@, could you please take a look?.
Thank you.
Project Member

Comment 2 by ClusterFuzz, Mar 18 2017

ClusterFuzz has detected this issue as fixed in range 457732:457736.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  process_ > 0 in process_posix.cc
  base::Process::Terminate
  task_manager::Task::Kill
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=409040:409094
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=457732:457736

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv978J5qCeJDo-V8Y_3MtSYfO2I_HDwgD-azKH3jp9wHYjeDndfOvqOuTwPPw9ygK2A_ghl-L_yuzX_kLML1E2pNlPCt3sayctHRMomjLfB6FEZ02PZVKpVlQ15I6QMeeiYzEZ8vma44U5RYB8XfRx6gRkdL9ku6CZkdWlcIrPKuR231E1WpX4kl6V36uoQMoIhdd7x5jnFgzklHEO0UNhQubjm-7d_q99GE6e71tLuuXJws1bHt07QmoDmM8Ud5-K1uDyWLiGBOkmtTzt68-fxDy37l5HfgeRDOcIkG_Hi4aOgvfmxNbrej4nM25ZStyWGczTaqNADApeNS8UsciD_pct83gFq6CIyJk3gMJD5KFkNNEvUwAv5oKQtMakBYf4KROiiPtoSm5e79-k6QBQskciPIOKQ?testcase_id=6711913582166016


Additional requirements: Requires Gestures

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 18 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 6711913582166016 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