MashLogin: BluetoothAdapterBlueZ::SetDiscoverable crash after sign-in |
||
Issue descriptionHappened on desktopui_MashLogin_SERVER_JOB Failure on tricky-tot-chrome-pfq-informational/R72-11210.0.0-b3086418 The test itself passes but chrome crashed during tests. This particular one tracks the crash in BluetoothAdapterBlueZ::SetDiscoverable. It does not really look like mash related though. logs: https://stainless.corp.google.com/browse/chromeos-autotest-results/253724756-chromeos-test/chromeos4-row2-rack3-host12/debug/ artifacts: https://pantheon.corp.google.com/storage/browser/chromeos-image-archive/tricky-tot-chrome-pfq-informational/R72-11210.0.0-b3086418 Stack ==== Thread 0 (crashed) 0 chrome!bluez::BluetoothAdapterBlueZ::SetDiscoverable(bool, base::RepeatingCallback<void ()> const&, base::RepeatingCallback<void ()> const&) [bluetooth_adapter_bluez.cc : 341 + 0x0] rax = 0x422af6d366f48f00 rdx = 0x00007ffcc4120e10 rcx = 0x00007ffcc4120e18 rbx = 0x000039fbc1863c70 rsi = 0x0000000000000001 rdi = 0x0000000000000000 rbp = 0x00007ffcc4120e00 rsp = 0x00007ffcc4120c90 r8 = 0x0000000000000016 r9 = 0x0000000000000002 r10 = 0x00007efdbc68aca9 r11 = 0x00007efdb1a3f1a0 r12 = 0x00007ffcc4120e18 r13 = 0x000039fbc1434b00 r14 = 0x000039fbc1434b00 r15 = 0x0000000000000000 rip = 0x00007efdb72e6d54 Found by: given as instruction pointer in context 1 chrome!pairing_chromeos::BluetoothHostPairingController::OnCreateService(scoped_refptr<device::BluetoothSocket>) [bluetooth_host_pairing_controller.cc : 241 + 0xd] rbx = 0x000039fbc1863c70 rbp = 0x00007ffcc4120e50 rsp = 0x00007ffcc4120e10 r12 = 0x000039fbc1434b00 r13 = 0x000039fbc1434b00 r14 = 0x000039fbc1434b00 r15 = 0x0000000000000000 rip = 0x00007efdb55f842e Found by: call frame info 2 chrome!base::internal::Invoker<base::internal::BindState<void (pairing_chromeos::BluetoothControllerPairingController::*)(scoped_refptr<device::BluetoothSocket>), base::WeakPtr <pairing_chromeos::BluetoothControllerPairingController> >, void (scoped_refptr<device::BluetoothSocket>)>::Run(base::internal::BindStateBase*, scoped_refptr<device::BluetoothSocke t>&&) [bind_internal.h : 516 + 0x2] rbx = 0x0000000000000000 rbp = 0x00007ffcc4120e70 rsp = 0x00007ffcc4120e60 r12 = 0x000039fbc152fb28 r13 = 0x000039fbc2e46080 r14 = 0x000039fbc2910c60 r15 = 0x000039fbc152fb30 rip = 0x00007efdb55f6318 Found by: call frame info 3 chrome!base::internal::Invoker<base::internal::BindState<base::RepeatingCallback<void (scoped_refptr<device::BluetoothSocket>)>, scoped_refptr<bluez::BluetoothSocketBlueZ> >, v oid ()>::Run(base::internal::BindStateBase*) [callback.h : 129 + 0x3] rbx = 0x0000000000000000 rbp = 0x00007ffcc4120e90 rsp = 0x00007ffcc4120e80 r12 = 0x000039fbc152fb28 r13 = 0x000039fbc2e46080 r14 = 0x000039fbc2910c60 r15 = 0x000039fbc152fb30 rip = 0x00007efdb72f2581 Found by: call frame info 4 chrome!bluez::BluetoothSocketBlueZ::OnRegisterProfile(base::RepeatingCallback<void ()> const&, base::RepeatingCallback<void (std::__1::basic_string<char, std::__1::char_traits< char>, std::__1::allocator<char> > const&)> const&, bluez::BluetoothAdapterProfileBlueZ*) [callback.h : 129 + 0x3] rbx = 0x0000000000000000 rbp = 0x00007ffcc4121010 rsp = 0x00007ffcc4120ea0 r12 = 0x000039fbc152fb28 r13 = 0x000039fbc2e46080 r14 = 0x000039fbc2910c60 r15 = 0x000039fbc152fb30 rip = 0x00007efdb73048fe Found by: call frame info 5 chrome!bluez::BluetoothAdapterBlueZ::SetProfileDelegate(device::BluetoothUUID const&, dbus::ObjectPath const&, bluez::BluetoothProfileServiceProvider::Delegate*, base::Repeatin gCallback<void (bluez::BluetoothAdapterProfileBlueZ*)> const&, base::RepeatingCallback<void (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > c onst&)> const&) [callback.h : 129 + 0x3] rbx = 0x000039fbc1864718 rbp = 0x00007ffcc4121090 rsp = 0x00007ffcc4121020 r12 = 0x000039fbc0f1d538 r13 = 0x000039fbc2e46080 r14 = 0x0000000000000000 r15 = 0x000039fbc1864778 rip = 0x00007efdb72ee51e Found by: call frame info 6 chrome!bluez::BluetoothAdapterBlueZ::OnRegisterProfile(device::BluetoothUUID const&, std::__1::unique_ptr<bluez::BluetoothAdapterProfileBlueZ, std::__1::default_delete<bluez::B luetoothAdapterProfileBlueZ> >) [callback.h : 129 + 0x3] rbx = 0x000039fbc1863cd0 rbp = 0x00007ffcc41210e0 rsp = 0x00007ffcc41210a0 r12 = 0x000039fbc168f968 r13 = 0x000039fbc0f1d570 r14 = 0x000039fbc0f1d568 r15 = 0x000039fbc1863ce0 rip = 0x00007efdb72ee636 Found by: call frame info
,
Oct 31
Is this in multi-process mash?
,
Oct 31
Yes, the crash happened with "--enable-features=Mash" during desktopui_MashLogin tests.
,
Oct 31
Gio, any ideas?
,
Oct 31
I'm new to ChromeOS so I'm not familiar with these tests. A couple of questions: Are these manual tests? If so, where could I find out what the test does? If not, where's the code for the test? Was this done on a VM or a real device?
,
Nov 1
It is an autotest. The suite name is desktopui_MashLogin, which does a sanity login test under mash. Code link is [1] The crash happened on a real device (BOARD=tricky) in lab, not sure whether it is specific to that hardware. You can run an autotest on device using "test_that" from your chromeos chroot. test_that --board=$BOARD $DUT_IP desktopui_MashLogin Also check out James' notes [2], "Autotests" section. [1] https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/site_tests/desktopui_MashLogin/desktopui_MashLogin.py?type=cs&q=desktopui_MashLogin&sq=file:%5Esrc+package:%5Echromeos_(internal%7Cpublic)$&g=0&l=18 [2] https://docs.google.com/document/d/1wn8NtyQi92Z6dOJuhyecG-7YFlpcVr_RVQvoWgCrYTg/edit?usp=sharing
,
Nov 12
Sorry for the delay. It took me a while to get everything set up. I haven't been able to reproduce by running test_that --board=$BOARD $DUT_IP desktopui_MashLogin on an eve. Is this still happening? |
||
►
Sign in to add a comment |
||
Comment 1 by xiy...@chromium.org
, Oct 31