New issue
Advanced search Search tips

Issue 866275 link

Starred by 1 user
Status: Assigned
Owner:
fdoray@chromium.org
Cc:
xhw...@chromium.org
kkaluri@chromium.org
robliao@chromium.org
gab@chromium.org
fdoray@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in base::CreateThread

Project Member Reported by ClusterFuzz, Jul 21 
Detailed report: https://clusterfuzz.com/testcase?key=4996459628593152

Fuzzer: afl_media_pipeline_integration_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900001ce1
Crash State:
  base::CreateThread
  base::internal::SchedulerWorker::Start
  base::internal::SchedulerWorkerPoolImpl::CreateRegisterAndStartSchedulerWorkerLo
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=569108:569115

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jul 21

Components: Internals>Core Internals>TaskScheduler
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, Jul 21

Cc: xhw...@chromium.org
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, Jul 27

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

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

Suspect CL: https://chromium.googlesource.com/chromium/src/+/6e1b000c47e97713e80e39f269cc3cdf679c564e

fdoray@ -- Could you please look into this issue.

Thanks!
►

Sign in to add a comment