New issue
Advanced search Search tips

Issue 839193 link

Starred by 3 users
Status: WontFix
Owner:
gogerald@chromium.org
Closed: Sep 20
Cc:
pnangunoori@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in payments::PaymentRequestSpec::UpdateSelectedShippingOption

Project Member Reported by ClusterFuzz, May 3 2018 
Detailed report: https://clusterfuzz.com/testcase?key=4656197324767232

Fuzzer: mojo_fuzzer
Job Type: linux_asan_chrome_mojo
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  payments::PaymentRequestSpec::UpdateSelectedShippingOption
  payments::PaymentRequestSpec::RecomputeSpecForDetails
  payments::mojom::PaymentRequestStubDispatch::Accept
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mojo&range=555295:555297

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4656197324767232

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
Project Member

Comment 1 by ClusterFuzz, May 3 2018

Components: UI>Browser>Payments
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Comment 2 by pnangunoori@chromium.org, May 3 2018

Cc: pnangunoori@chromium.org
Labels: Test-Predator-Wrong CF-NeedsTriage
Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.
Thank You.

Comment 3 by pnangunoori@chromium.org, May 3 2018

Labels: M-68

Comment 4 by ma...@chromium.org, May 3 2018

Owner: gogerald@chromium.org
Status: Assigned (was: Untriaged)

Comment 5 by gogerald@chromium.org, May 4 2018 

The stack trace doesn't make sense to me, is possible that the stack trace is wrong?
Project Member

Comment 6 by ClusterFuzz, Jul 26

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 4656197324767232 appears to be flaky, updating reproducibility label.
Project Member

Comment 7 by ClusterFuzz, Sep 20

Status: WontFix (was: Assigned)
ClusterFuzz testcase 4656197324767232 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