New issue
Advanced search Search tips

Issue 856881 link

Starred by 1 user
Status: Duplicate
Owner:
blundell@chromium.org
Closed: Jul 12
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: g_dbus_thread_manager. DBusThreadManager::Get() called before Initialize() in db

Project Member Reported by ClusterFuzz, Jun 27 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6564107827019776

Fuzzer: inferno_twister_c
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  g_dbus_thread_manager. DBusThreadManager::Get() called before Initialize() in db
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=567259:567260

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

Additional requirements: Requires HTTP

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jun 27 2018

Labels: Test-Predator-Auto-Owner
Owner: blundell@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/8e9dbcd3188c015f2dd67ba781168431aa51dab5 (Have Device Service observe MessageLoop destruction).

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 2 by blundell@chromium.org, Jun 27 2018

Status: Started (was: Assigned)
Project Member

Comment 3 by ClusterFuzz, Jul 12

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

Comment 4 by ClusterFuzz, Jul 12

Status: WontFix (was: Started)
ClusterFuzz testcase 6564107827019776 is flaky and no longer crashes, so closing issue.

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

Comment 5 by blundell@chromium.org, Jul 12

Labels: ClusterFuzz-Wrong
There is definitely a real issue here, which I am working on.

Comment 6 by blundell@chromium.org, Jul 12

Mergedinto: 856771
Status: Duplicate (was: WontFix)
►

Sign in to add a comment