Null-dereference READ in payments::PaymentRequest::Abort |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6482881409712128 Fuzzer: mojo_fuzzer Job Type: linux_asan_chrome_mojo Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x0000000000f0 Crash State: payments::PaymentRequest::Abort payments::mojom::PaymentRequestStubDispatch::Accept mojo::InterfaceEndpointClient::HandleValidatedMessage Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mojo&range=546453:546454 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6482881409712128 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
May 2 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/e1faaeeaacb7ba4f2d799374be9a83e4902d3b11 ([iOS Password Manager] Show suggestions on password fields.). 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.
,
May 3 2018
The suspected CL is only for iOS, so it can't be culprit of this issue.
,
May 3 2018
,
May 4 2018
The report indicates below codes caused a Null-dereference. Do not know how this could happen. Is it possible that the stack trace is wrong? std::unique_ptr<PaymentResponseHelper> response_helper_; !!response_helper_;
,
Jul 26
ClusterFuzz testcase 6482881409712128 appears to be flaky, updating reproducibility label.
,
Jul 26
ClusterFuzz testcase 6482881409712128 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ClusterFuzz
, May 2 2018Labels: Test-Predator-Auto-Components