New issue
Advanced search Search tips

Issue 767795 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
mac-bugs-priority@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in base::PowerMonitorSource::ProcessPowerEvent

Project Member Reported by ClusterFuzz, Sep 22 2017 
Detailed report: https://clusterfuzz.com/testcase?key=4599112761868288

Fuzzer: meacer_extension_apis
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  base::PowerMonitorSource::ProcessPowerEvent
  device::mojom::PowerMonitorClientStubDispatch::Accept
  mojo::InterfaceEndpointClient::HandleValidatedMessage
  
Sanitizer: address (ASAN)

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

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.

Comment 1 by pnangunoori@chromium.org, Sep 22 2017

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 2 by lgrey@chromium.org, Sep 22 2017

Status: Available (was: Untriaged)
Project Member

Comment 3 by ClusterFuzz, Oct 1 2017

Components: Internals>Core Internals>Mojo
Labels: Test-Predator-AutoComponents
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

Comment 4 by yzshen@chromium.org, Oct 2 2017

Components: -Internals>Mojo
Labels: Test-Predator-Wrong-Components
This doesn't seem like a core Mojo platform issue. Removing Internals>Mojo
Project Member

Comment 5 by ClusterFuzz, Nov 7 2017

Labels: M-64 ClusterFuzz-Top-Crash ReleaseBlock-Beta
Testcase 4599112761868288 is a top crash on ClusterFuzz for mac platform. Please prioritize fixing this crash.

Marking this crash as a Beta release blocker.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Comment 6 by mbarbe...@chromium.org, Nov 7 2017

Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components

Comment 7 by ajha@chromium.org, Nov 23 2017 

This is marked as Beta blocker for M-64 and would be good to have all the Beta blockers resolved before branch point. M-64 will be branched in 1 week from now.

Requesting someone from the Mac team to have a look at this and help in further investigation.

Comment 8 by jmukthavaram@chromium.org, Dec 4 2017 

Friendly ping to get an update on this issue as it is marked as beta blocker.
Thanks..!

Comment 9 by manoranj...@chromium.org, Dec 6 2017

Labels: -ReleaseBlock-Beta
This is 'Unreproducible' CF report, not sure 'RB-Beta' still make sense here?
Project Member

Comment 10 by ClusterFuzz, Dec 15 2017

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