New issue
Advanced search Search tips

Issue 899540 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 11
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in mojo::core::ports::UserMessageEvent::~UserMessageEvent

Project Member Reported by ClusterFuzz, Oct 28

Issue description

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

Fuzzer: inferno_twister_c
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  mojo::core::ports::UserMessageEvent::~UserMessageEvent
  mojo::core::Core::DestroyMessage
  service_manager::mojom::Service_OnBindInterface_ProxyToResponder::Run
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=603357:603358

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Oct 28

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.
In my experience, there are reasons to check for a NULL pointer other than dereferencing it. A common memory-leak idiom is reallocating storage and assigning its address to a pointer that already points to allocated storage. The correct idiom is to only allocate storage if the pointer is currently NULL. But nowhere in that particular idiom would a NULL pointer necessarily be referenced. https://www.brotherprintersupportnumber.com/blog/how-to-fix-printer-keeps-going-offline-error/, should you have any questions or comments, please let me know.

Cc: kkaluri@chromium.org
Labels: M-72 Test-Predator-Wrong
Owner: rockot@google.com
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using Code Search for the file, "ports/event.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/0db0bcf5fb39232fc705cc34b4c617ec463f0092

rockot@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!
Project Member

Comment 4 by ClusterFuzz, Nov 3

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

Comment 5 by ClusterFuzz, Nov 11

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