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

Issue 665248 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Last visit > 30 days ago
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Crash in bluetooth on exiting docked mode

Project Member Reported by abodenha@chromium.org, Nov 15 2016

Issue description

Version: 56.0.2917.0 8986.0.0 canary-channel samus
OS: Chrome

What steps will reproduce the problem?
(1) Connect a Pluggable USB-C Triple display docking station to display and eithernet.
(2) Close the laptop (enter docked mode)
(3) Open the laptop (exit docked mode)

What is the expected result?
Exit docked mode normally

What happens instead?
Both internal and external displays show briefly, the browser crash.
https://crash.corp.google.com/browse?q=reportid=%276e715a2f00000000%27#0

rkc@ can you route appropriately?


 
I'm unable to repro. I had been trying to repro an issue with smartlock a bit earlier.  I'll fiddle and see if I can get a more reliable repro.

Comment 2 by st...@chromium.org, Nov 15 2016

Cc: hennessywill@chromium.org snanda@chromium.org
Owner: mcchou@chromium.org
Hey Miao, does this look like it could be a BlueZ related crash?

Since this is happening on the logic screen, this could be related with Smartlock code, but since the crash is in BlueZ; we should look into fixing it any way.

Cc: tengs@chromium.org

Comment 4 by mcchou@chromium.org, Nov 18 2016

Hello Albert,

The issue summary confused me a bit. The version of Chrome OS in the crash report(https://crash.corp.google.com/browse?q=reportid=%276e715a2f00000000%27#0) is 8968.0.0 which is different from the version 8986.0.0.

According to the Chrome OS version of the crash report(8968.0.0), bluetoothd crashed at the same function call as issue 662144. The fix has landed in 8972.0.0. So I will merge this into issue 662144. Feel free to reopen the issue if you still see this issue with builds newer than 8972.0.0.

Comment 5 by mcchou@chromium.org, Nov 18 2016

Mergedinto: 662144
Status: Duplicate (was: Assigned)

Sign in to add a comment