New issue
Advanced search Search tips

Issue 789235 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Blocking:
issue 507419



Sign in to add a comment

Bluetooth classic crash when using BLE

Project Member Reported by cco3@chromium.org, Nov 28 2017

Issue description

I've run into a crash when using https://operasoftware.github.io/bb8/ with a BB8 device.
The crash is in the BT classic stack rather than in BLE.

[27232:17416:1128/111728.182:FATAL:scoped_handle.cc(116)] Check failed: false. 
Backtrace:
        base::debug::StackTrace::StackTrace [0x0000000000A131D8+104] (C:\src\chromium\src\base\debug\stack_trace_win.cc:286)
        base::debug::StackTrace::StackTrace [0x0000000000A11E1F+31] (C:\src\chromium\src\base\debug\stack_trace.cc:199)
        logging::LogMessage::~LogMessage [0x0000000000A88EB3+131] (C:\src\chromium\src\base\logging.cc:581)
        `anonymous namespace'::CloseHandleWrapper [0x0000000000E3B952+130] (C:\src\chromium\src\base\win\scoped_handle.cc:117)
        `anonymous namespace'::ActiveVerifier::CloseHandle [0x0000000000E38A2F+47] (C:\src\chromium\src\base\win\scoped_handle.cc:174)
        base::win::HandleTraits::CloseHandle [0x0000000000E38468+40] (C:\src\chromium\src\base\win\scoped_handle.cc:267)
        base::win::GenericScopedHandle<base::win::HandleTraits,base::win::VerifierTraits>::Close [0x000000002188A327+103] (C:\src\chromium\src\base\win\scoped_handle.h:104)
        base::win::GenericScopedHandle<base::win::HandleTraits,base::win::VerifierTraits>::Set [0x0000000021889FDA+58] (C:\src\chromium\src\base\win\scoped_handle.h:73)
        device::win::BluetoothClassicWrapper::FindFirstRadio [0x0000000021889F3E+110] (C:\src\chromium\src\device\bluetooth\bluetooth_classic_win.cc:43)
        device::BluetoothTaskManagerWin::PollAdapter [0x0000000021948FA6+294] (C:\src\chromium\src\device\bluetooth\bluetooth_task_manager_win.cc:383)
        base::internal::FunctorTraits<void (device::BluetoothTaskManagerWin::*)(),void>::Invoke<const scoped_refptr<device::BluetoothTaskManagerWin> &> [0x000000002195D323+67] (C:\src\chromium\src\base\bind_internal.h:194)
        base::internal::InvokeHelper<0,void>::MakeItSo<void (device::BluetoothTaskManagerWin::*const &)(),const scoped_refptr<device::BluetoothTaskManagerWin> &> [0x000000002195D24D+93] (C:\src\chromium\src\base\bind_internal.h:277)
        base::internal::Invoker<base::internal::BindState<void (device::BluetoothTaskManagerWin::*)(),scoped_refptr<device::BluetoothTaskManagerWin> >,void ()>::RunImpl<void (device::BluetoothTaskManagerWin::*const &)(),const std::tuple<scoped_refptr<device::Blue [0x000000002195D1CB+75] (C:\src\chromium\src\base\bind_internal.h:351)
        base::internal::Invoker<base::internal::BindState<void (device::BluetoothTaskManagerWin::*)(),scoped_refptr<device::BluetoothTaskManagerWin> >,void ()>::Run [0x000000002195D0CD+61] (C:\src\chromium\src\base\bind_internal.h:333)
        base::OnceCallback<void ()>::Run [0x000000000099358E+94] (C:\src\chromium\src\base\callback.h:65)
        base::debug::TaskAnnotator::RunTask [0x0000000000A1794A+778] (C:\src\chromium\src\base\debug\task_annotator.cc:57)
        base::internal::TaskTracker::RunOrSkipTask [0x0000000000C91E31+2241] (C:\src\chromium\src\base\task_scheduler\task_tracker.cc:409)
        base::internal::TaskTracker::RunNextTask [0x0000000000C901BB+715] (C:\src\chromium\src\base\task_scheduler\task_tracker.cc:312)
        base::internal::SchedulerWorker::Thread::ThreadMain [0x0000000000C7571B+923] (C:\src\chromium\src\base\task_scheduler\scheduler_worker.cc:72)
        base::`anonymous namespace'::ThreadFunc [0x0000000000CA7EDC+412] (C:\src\chromium\src\base\threading\platform_thread_win.cc:91)
        BaseThreadInitThunk [0x00007FFC55358364+20]
        RtlUserThreadStart [0x00007FFC57847091+33]

The relevant BT code is here:
https://cs.chromium.org/chromium/src/device/bluetooth/bluetooth_classic_win.cc?l=43

I've not been able to reproduce this issue.
 

Comment 1 by cco3@chromium.org, Nov 28 2017

Cc: gogerald@chromium.org
gogerald@, would you be able to comment on this issue?  Is there anything that stands out as potentially problematic in FindFirstRadio method?

Comment 2 by cco3@chromium.org, Nov 28 2017

Status: Assigned (was: Untriaged)
Owner: ----
Status: Untriaged (was: Assigned)
Marking issues assigned to cco3@ as untriaged as they are no longer working on Chromium.
Mergedinto: 820864
Status: Duplicate (was: Untriaged)

Sign in to add a comment