New issue
Advanced search Search tips

Issue 736226 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug

Blocking:
issue 580406


Show other hotlists

Hotlists containing this issue:
web-bluetooth


Sign in to add a comment

bluetooth: Notifications stop after 3 concurrent startNotifications calls.

Project Member Reported by ortuno@chromium.org, Jun 23 2017

Issue description

The following layout test fails when moving it over to the new framework:

https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/bluetooth/characteristic/notifications/concurrent-starts.html?type=cs&q=concurrent-starts.h&sq=package:chromium&l=1

'use strict';
promise_test(() => {
  return setBluetoothFakeAdapter('HeartRateAdapter')
    .then(() => requestDeviceWithKeyDown({
      filters: [{services: ['heart_rate']}]}))
    .then(device => device.gatt.connect())
    .then(gattServer => gattServer.getPrimaryService('heart_rate'))
    .then(service => service.getCharacteristic('heart_rate_measurement'))
    .then(characteristic => Promise.all([
      characteristic.startNotifications(),
      characteristic.startNotifications(),
      characteristic.startNotifications()]));
  // TODO(ortuno): Assert that notifications are active.
  // http://crbug.com/600762
}, 'Multiple starts in a row.');

It seems that after the startNotifications calls the end state is "Not subscribed". Probably a problem with how we do queuing in the underlying layer, currently writing a device_unittest to check.
 

Comment 1 by ortuno@chromium.org, Jun 23 2017

Test that reproduces the bug: https://chromium-review.googlesource.com/#/c/544386/
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 25 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)

Sign in to add a comment