New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 894972 link

Starred by 2 users
Status: WontFix
Owner:
█ farahcharab@chromium.org
Last visit > 30 days ago
Closed: Dec 1
Cc:
█ farahcharab@google.com
kkaluri@chromium.org
altimin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in _pthread_key_global_init

Project Member Reported by ClusterFuzz, Oct 12 
Detailed report: https://clusterfuzz.com/testcase?key=5752821088256000

Fuzzer: libFuzzer_sequence_manager_fuzzer
Job Type: mac_libfuzzer_chrome_asan
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  _pthread_key_global_init
  base::sequence_manager::ThreadManager::GetTaskQueueFor
  base::sequence_manager::ThreadManager::PostDelayedTask
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=596756:596813

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
Project Member

Comment 1 by ClusterFuzz, Oct 12

Components: Blink>Scheduling
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.
Project Member

Comment 2 by ClusterFuzz, Oct 12

Cc: farahcharab@google.com
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Comment 3 by kkaluri@chromium.org, Oct 16

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

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

Suspect CL: https://chromium.googlesource.com/chromium/src/+/f67097b4acac3a85de15f259ee38295da301802e

farahcharab@ -- 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, Dec 1

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

Comment 5 by ClusterFuzz, Dec 1

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