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

Issue 923024 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression



Sign in to add a comment

CHECK failure: initialized_ in test_timeouts.h

Project Member Reported by ClusterFuzz, Jan 17 (5 days ago)

Issue description

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

Fuzzer: libFuzzer_renderer_tree_fuzzer
Fuzz target binary: renderer_tree_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  initialized_ in test_timeouts.h
  TestTimeouts::action_max_timeout
  base::test::ScopedTaskEnvironment::ScopedTaskEnvironment
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=621021:621022

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
 
Project Member

Comment 1 by ClusterFuzz, Jan 17 (5 days ago)

Components: Internals>Core
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, Jan 17 (5 days ago)

Cc: aizatsky@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.
Project Member

Comment 3 by ClusterFuzz, Jan 17 (5 days ago)

Labels: Test-Predator-Auto-Owner
Owner: w...@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/d9e4cb77324a3d4e0dfd6b599ce34e1224fdedb6 (Apply a default timeout to RunLoop::Run() calls on test main threads.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Comment 4 by w...@chromium.org, Jan 17 (5 days ago)

Labels: -Type-Bug M-73 Type-Bug-Regression
Status: Started (was: Assigned)

Comment 5 by w...@chromium.org, Jan 17 (5 days ago)

Probably sufficient just to TestTimeouts::Initialize() in the fuzzer_support Env().
Project Member

Comment 6 by bugdroid1@chromium.org, Today (11 hours ago)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2af0691c5e48642c68ee60ad873838e8a94292c5

commit 2af0691c5e48642c68ee60ad873838e8a94292c5
Author: Wez <wez@chromium.org>
Date: Tue Jan 22 18:56:04 2019

Fix //content's fuzzer_support Env() helper to initialize TestTimeouts.

Fuzzers based on RenderViewTest need TestTimeouts to be initialized so
that the RenderViewTest's internal ScopedTaskEnvironment can use them.

Bug: 923024
Change-Id: I31d655486db89ce2daf7fff56b8564734ce544cb
Reviewed-on: https://chromium-review.googlesource.com/c/1420558
Reviewed-by: Jonathan Metzman <metzman@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Commit-Queue: Max Moroz <mmoroz@chromium.org>
Auto-Submit: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#624851}
[modify] https://crrev.com/2af0691c5e48642c68ee60ad873838e8a94292c5/content/test/fuzzer/BUILD.gn
[modify] https://crrev.com/2af0691c5e48642c68ee60ad873838e8a94292c5/content/test/fuzzer/fuzzer_support.cc

Sign in to add a comment