New issue
Advanced search Search tips

Issue 660548 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Crash in begin

Project Member Reported by ClusterFuzz, Oct 28 2016

Issue description

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5590736952360960

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000010
Crash State:
  begin
  wm::TransientWindowManager::RemoveTransientChild
  wm::TransientWindowManager::OnWindowDestroying
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_content_shell_drt&range=428077:428348

Minimized Testcase (7.86 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97ykppU3YrFcBvxi9PIqreJ9Uz1DOrZW29Yip5ewhVSPqRl5X0KVvZYiU0FiwcKBdNkSXD-8QLHUVYJuz6DqNh8YszubV7Ca6IHwMrFEQrDEcINVcG4DQi_mhN0XhSiO_dLex0EA9qhhYw1LTnW7QtjcNCqCA?testcase_id=5590736952360960

Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Components: UI>Shell>WindowManager
Labels: M-56 Te-Logged
Owner: sky@chromium.org
Status: Assigned (was: Untriaged)
Author: sky
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/f8fcebc79eae73281b270ae26c8248f757fb0570
Time: Thu Oct 27 18:34:13 2016
Lines 95 of file transient_window_manager.cc which potentially caused crash are changed in this cl (frame #2, "wm::TransientWindowManager::RemoveTransientChild").
Minimum distance from crash line to modified line: 0. (file: transient_window_manager.cc, crashed on: 93, modified: 93).

Suspected Project: chromium

Comment 2 by sky@chromium.org, Oct 31 2016

Status: Started (was: Assigned)
Project Member

Comment 3 by bugdroid1@chromium.org, Oct 31 2016

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

commit 8634758638eb923138722ccfc16e2c5a2d965a2f
Author: sky <sky@chromium.org>
Date: Mon Oct 31 19:27:48 2016

Fixes possible crash in content shell shutdown

Destruction of WMState needs to be after ShellPlatformDataAura.

BUG= 660548 
TEST=covered by tests
R=ben@chromium.org

Review-Url: https://codereview.chromium.org/2459413002
Cr-Commit-Position: refs/heads/master@{#428767}

[modify] https://crrev.com/8634758638eb923138722ccfc16e2c5a2d965a2f/content/shell/browser/shell_views.cc

Comment 4 by sky@chromium.org, Oct 31 2016

Status: Fixed (was: Started)

Comment 5 by sky@chromium.org, Oct 31 2016

Cc: sky@chromium.org
 Issue 660641  has been merged into this issue.
Project Member

Comment 6 by ClusterFuzz, Nov 2 2016

ClusterFuzz has detected this issue as fixed in range 428740:428928.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5590736952360960

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000000000010
Crash State:
  begin
  wm::TransientWindowManager::RemoveTransientChild
  wm::TransientWindowManager::OnWindowDestroying
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_content_shell_drt&range=428077:428348
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_content_shell_drt&range=428740:428928

Minimized Testcase (7.86 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97ykppU3YrFcBvxi9PIqreJ9Uz1DOrZW29Yip5ewhVSPqRl5X0KVvZYiU0FiwcKBdNkSXD-8QLHUVYJuz6DqNh8YszubV7Ca6IHwMrFEQrDEcINVcG4DQi_mhN0XhSiO_dLex0EA9qhhYw1LTnW7QtjcNCqCA?testcase_id=5590736952360960

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 7 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment