Canary crash on requestDevice from chrome extension (was working on previous canary release)
Reported by
ogil...@gmail.com,
Aug 11 2016
|
|||||||||||||||
Issue description
Chrome Version : Version 54.0.2826.0 canary (64-bit) (Mac)
URLs : Chrome extension
Other browsers tested:
have tested this issue:
Chromium OS : OK
Canary OS : FAIL
What steps will reproduce the problem?
(1) requestDevice with service 00001808-0000-1000-8000-00805f9b34fb
(2) Canary crashes immediatly, impossible to see any log
Same operations in chromium os with same extension works fine. Using BLE via chrome extension, multiple times, I've never seen the device popup chooser.
BLE connexions with web bluetooth samples in Canary works fine.
This extension and connect method was working on previous canary release (number ???)
What is the expected result?
My Nexus 6 is find and connection to gatt server is initiated
What happens instead?
Canary crashes
Please provide any additional information below. Attach a screenshot if
possible.
Crash report attach below
Olivier
,
Aug 11 2016
And if so could you paste the crash id here?
,
Aug 11 2016
,
Aug 11 2016
Here is one of the crash id :
b56d09a8-aaac-41ec-9a58-174ad932ff2b
and the server id :
3c9c144100000000
Le 11/08/2016 à 17:28, ort… via monorail a écrit :
,
Aug 11 2016
Ah I see what the problem is: https://chromium.googlesource.com/chromium/src/+/master/content/browser/bluetooth/bluetooth_device_chooser_controller.cc#312 That line is not returning.
,
Aug 12 2016
I've just reproduced this issue and I confirm it crashes when calling navigator.bluetooth.requestDevice from a Chrome Extension background page and a Chrome Extension popup page (browserAction). However it doesn't crash from a chrome-extension://<extension_id>/page.html tab. @juncai I understand why a background page would not trigger Bluetooth chooser but why not from a popup page?
,
Aug 12 2016
I had a fix yesterday but didn't realize it didn't land. http://crrev.com/2238973002
,
Aug 12 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b38275d302118a3c5d8437314e08481c8a167d32 commit b38275d302118a3c5d8437314e08481c8a167d32 Author: ortuno <ortuno@chromium.org> Date: Fri Aug 12 15:55:52 2016 bluetooth: Add missing return when bluetooth not supported. This was causing a null pointer derefence in line 317. BUG= 636976 Review-Url: https://codereview.chromium.org/2238973002 Cr-Commit-Position: refs/heads/master@{#411663} [modify] https://crrev.com/b38275d302118a3c5d8437314e08481c8a167d32/content/browser/bluetooth/bluetooth_device_chooser_controller.cc
,
Aug 12 2016
,
Aug 14 2016
Hi all, As I can't establish a ble connexion from a background page, is there a possibility to maintain a ble connexion active (established from a tab) if I close the tab ? In other words, can I pass the connected device object from my extension tab to my long lived background chrome extension ? Thanks Olivier Le 12/08/2016 à 18:00, ort… via monorail a écrit :
,
Aug 29 2016
,
Aug 31 2016
Hi Olivier, You can't yet do that. See https://github.com/WebBluetoothCG/web-bluetooth/issues/57#issuecomment-208632357 for some background. What is your use case?
,
Oct 7 2016
,
Nov 19 2016
,
Jan 21 2017
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Oct 14 2017
|
|||||||||||||||
►
Sign in to add a comment |
|||||||||||||||
Comment 1 by ortuno@chromium.org
, Aug 11 2016