New issue
Advanced search Search tips

Issue 906405 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 13
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-12-10
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in mojo::core::Core::CreateMessage

Project Member Reported by ClusterFuzz, Nov 18

Issue description

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

Fuzzer: inferno_twister_c
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000080
Crash State:
  mojo::core::Core::CreateMessage
  mojo::Message::Message
  resource_coordinator::mojom::blink::ProcessCoordinationUnitProxy::SetExpectedTas
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

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

Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
 
Project Member

Comment 1 by ClusterFuzz, Nov 18

Components: Internals>Mojo
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.
Cc: oksamyt@chromium.org rockot@google.com
NextAction: 2018-12-10
Looks like an allocation-related crash. Will check back after Dec 10 to see if it reproduces again. 
Cc: kkaluri@chromium.org
Labels: Test-Predator-Wrong CF-NeedsTriage
Unable to provide possible suspect using Predator, CL and Code Search.
CC'ing rockot@ for further triage.

Thank You...
The NextAction date has arrived: 2018-12-10
Project Member

Comment 5 by ClusterFuzz, Dec 13

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