Crash in void JSMethod<app, &app::setTimeOut> |
|||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5386535252000768 Fuzzer: attekett_surku_fuzzer Job Type: linux_asan_chrome_mp Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000000000008 Crash State: void JSMethod<app, &app::setTimeOut> v8::internal::FunctionCallbackArguments::Call v8::internal::Builtin_Impl_HandleApiCall Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_mp&range=296165:296183 Minimized Testcase (202.85 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96FaoKrUHCSiiBIyPdYfATV3fABWcib8ByPIvmgHratiKqoX0xwNWlKFat0zkM8hoGQZgArW6KeK283zRFgY-9Z7kNWHCoFPOYmDGqQGTVH9PY9ILY2d0CmkM5RSrLm7xq2c_unqUKuq2towP4VjBMwcMKCG-zMs8kuxHtoM38KXhBzJEI?testcase_id=5386535252000768 Filer: ssamanoori See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jul 5 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 8 2016
ClusterFuzz has detected this issue as fixed in range 403906:404161. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5386535252000768 Fuzzer: attekett_surku_fuzzer Job Type: linux_asan_chrome_mp Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000000000008 Crash State: void JSMethod<app, &app::setTimeOut> v8::internal::FunctionCallbackArguments::Call v8::internal::Builtin_Impl_HandleApiCall Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_mp&range=296165:296183 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_mp&range=403906:404161 Minimized Testcase (202.85 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96FaoKrUHCSiiBIyPdYfATV3fABWcib8ByPIvmgHratiKqoX0xwNWlKFat0zkM8hoGQZgArW6KeK283zRFgY-9Z7kNWHCoFPOYmDGqQGTVH9PY9ILY2d0CmkM5RSrLm7xq2c_unqUKuq2towP4VjBMwcMKCG-zMs8kuxHtoM38KXhBzJEI?testcase_id=5386535252000768 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.
,
Jul 8 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Oct 18 2016
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ssamanoori@chromium.org
, Jul 4 2016Components: Tools>Test>FindIt>WrongResult
Labels: findit-wrong Te-Logged M-53
Owner: verwa...@chromium.org
Status: Assigned (was: Available)