Issue metadata
Sign in to add a comment
|
Minnie: BT scanning causes chrome crash |
||||||||||||||||||||||
Issue descriptionVersion:8968.0.0 (Official Build) dev-channel veyron_Minnie What steps will reproduce the problem? (1)Login to Minnie and device and make sure u enable "ARC++" (2)Now enable Bluetooth and try to scan devices from status tray or the settings page What is the expected output? The list of available devices should be seen What do you see instead? Chrome crash is seen Please use labels and text to provide additional information. Below are couple of crash Id's Crash ID Chrome (Server ID: ed9672a700000000) Crash ID Chrome (Server ID: 9b2c72a700000000)
,
Nov 8 2016
#CBC-RS/TC-watchlist
,
Nov 8 2016
http://crrev.com/2482323002 should fixes this. Look like something make mojo::String unhappy with nullptr.
,
Nov 9 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/68561070668c0f84a0cb2d3d9fc70129fb5ede1b commit 68561070668c0f84a0cb2d3d9fc70129fb5ede1b Author: puthik <puthik@chromium.org> Date: Wed Nov 09 00:27:59 2016 arc: bluetooth: Don't use nullptr with device name Don't use nullptr with the device name in mojo types below as they are not defined as nullable in mojom file. - mojom::BluetoothProperty.bdname - mojom::BluetoothAdvertisingData.local_name This fixes Chrome crash in recent build because of the Bluetooth API change in http://crrev.com/2440043002 that make the device name optional. Before that, GetName() will returns MAC address when there is no device name. BUG= 663096 TEST=minnie won't crash when scan for new BT device. nRF connect app still has same behavior. Review-Url: https://codereview.chromium.org/2482323002 Cr-Commit-Position: refs/heads/master@{#430789} [modify] https://crrev.com/68561070668c0f84a0cb2d3d9fc70129fb5ede1b/components/arc/bluetooth/arc_bluetooth_bridge.cc
,
Nov 9 2016
,
Nov 11 2016
verified on 56.0.2915.0 build on minnie. The BT scanning now works fine.
,
Mar 3 2017
,
Mar 3 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by puthik@chromium.org
, Nov 8 2016