New issue
Advanced search Search tips

Issue 828895 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Web Bluetooth Disconnect Issues When Closing Laptop

Reported by nall...@workbenchplatform.com, Apr 4 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
1. Connect a bluetooth device.
2. Close laptop once connection is complete.
3. Wait a few seconds.
4. Open laptop
5. If you logged it, you can see that "gattserverdisconnected" is called for the device.  But the device still thinks it is connected.
6. Refresh the browser and the device will finally disconnect

What is the expected behavior?
"gattserverdisconnected" is being called without actually disconnecting from the device.  I'd expect to actually disconnect from the device when chrome thinks it is disconnecting.

What went wrong?
Chrome thinks my device is disconnected, but my OS and device still know the device is connected.

Did this work before? Yes 

Chrome version: 65.0.3325.181  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

I recall a similar bug where Chrome would crash when I closed my laptop while a device was connected.  This was in May 2017.  I'm assuming after that ticket was marked as resolved that I was not experiencing this issue.  I don't test shutting my laptop very often, so I'm not sure how long this has been an issue.
 
I'm not sure if this is related but it was another instance where I was experiencing issues when shutting my laptop, https://bugs.chromium.org/p/chromium/issues/detail?id=719289
Labels: Needs-Triage-M65

Comment 3 by tkent@chromium.org, Apr 5 2018

Components: -Blink Blink>Bluetooth
Thanks for the report.

It's strange that the device stays connected. According to macOS's docs:

A state with a value lower than CBCentralManagerStatePoweredOn implies that scanning has stopped and that any connected peripherals have been disconnected.

That said, the bug be unrelated to the portion of the code that handles that state change.
Cc: jlebel@chromium.org
Labels: -Needs-Triage-M65
Status: Available (was: Unconfirmed)

Sign in to add a comment