I've got a case of osquery apparently in some kind of hard busy-loop, unresponsive, no longer running queries or logging. It's using a steady 16.7% cpu, and that's all in use by a single thread that's not one of the rocksdb threads. I attached GDB and got this backtrace from that thread:

#0  0x00007fa9bdeaf0f7 in std::_Rb_tree_increment(std::_Rb_tree_node_base const*) ()
#1  0x00007fa9bd5f5c9e in osquery::Config::scheduledQueries(std::function<void (std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osquery::ScheduledQuery const&)>) ()
#2  0x00007fa9bd6a4305 in osquery::SchedulerRunner::start() ()
#3  0x00007fa9bd6396be in osquery::InternalRunnable::run() ()
#4  0x00007fa9bd63a508 in std::thread::_Impl<std::_Bind_simple<std::_Bind<std::_Mem_fn<void (osquery::InternalRunnable::*)()> (osquery::InternalRunnable*)> ()> >::_M_run() ()
#5  0x00007fa9bdeb291a in execute_native_thread_routine ()
#6  0x00007fa9bbfe9184 in start_thread (arg=0x7fa9abfff700) at pthread_create.c:312
#7  0x00007fa9bc50f37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111