process_ > 0 in process_posix.cc |
||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5845487946301440 Fuzzer: inferno_layout_test_unmodified Job Type: linux_msan_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 Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_msan_chrome&range=409040:409094 Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94Illbwmr5E5AjWFkAIcy-Afcd6tdWjj_OsIgWHrxK-AtNlTEJsLk6glnDga5Y1YROOiPR-WRH6qzCmcXvrb1kE6rGsKl_LKOWeWtH7r5hXJrv2Wvp7cw1RHpQf-Vec0G51K_jvVYEYILHDVRsUGOgmDMuuUg?testcase_id=5845487946301440 Additional requirements: Requires Gestures Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Nov 30 2016
Unable to find to suspect from Find it. Assigning to the concern owner from CL https://chromium.googlesource.com/chromium/src/+log/17b73d696569a139b614b057bbddb13784c81ca9..e87c7c71ceb85ecfe84a43fd5c298ea6608e1e0d?pretty=fuller Suspecting the Commit -- https://chromium.googlesource.com/chromium/src/+/1824ae3ede49ac7e6cf6224d03e713fab8070c30 @nick -- Could you please look into the issue, kindly re-assign if this is not related to your change. Thank You.
,
Dec 15 2016
Ahmed, do you have any time to look at this? It seems clusterfuzz has found some way to wind up trying to kill a process (via the TaskManager) with a pid of zero. I'm not sure what this fuzzer is doing exactly, but it looks like it's driving random UI inputs.
,
Mar 10 2017
ClusterFuzz has detected this issue as fixed in range 456056:456103. Detailed report: https://clusterfuzz.com/testcase?key=5845487946301440 Fuzzer: inferno_layout_test_unmodified Job Type: linux_msan_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: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=409040:409094 Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=456056:456103 Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94Illbwmr5E5AjWFkAIcy-Afcd6tdWjj_OsIgWHrxK-AtNlTEJsLk6glnDga5Y1YROOiPR-WRH6qzCmcXvrb1kE6rGsKl_LKOWeWtH7r5hXJrv2Wvp7cw1RHpQf-Vec0G51K_jvVYEYILHDVRsUGOgmDMuuUg?testcase_id=5845487946301440 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.
,
Mar 11 2017
ClusterFuzz testcase 5845487946301440 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Mar 11 2017
ClusterFuzz has detected this issue as fixed in range 456056:456103. Detailed report: https://clusterfuzz.com/testcase?key=5845487946301440 Fuzzer: inferno_layout_test_unmodified Job Type: linux_msan_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: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=409040:409094 Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=456056:456103 Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94Illbwmr5E5AjWFkAIcy-Afcd6tdWjj_OsIgWHrxK-AtNlTEJsLk6glnDga5Y1YROOiPR-WRH6qzCmcXvrb1kE6rGsKl_LKOWeWtH7r5hXJrv2Wvp7cw1RHpQf-Vec0G51K_jvVYEYILHDVRsUGOgmDMuuUg?testcase_id=5845487946301440 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. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ajha@chromium.org
, Nov 30 2016