Unhandled exception from boost::thread::start_thread

Bug #683620 reported by Andrew Hutchings
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
High
Andrew Hutchings
7.0
Fix Released
High
Andrew Hutchings

Bug Description

Stack trace from core file. Hit when trying to generate > 1000 connections. Run the attached php file to reproduce this.

#0 0x0000003b9e20c94c in pthread_kill () from /lib64/libpthread.so.0
#1 0x0000000000660eda in write_core (sig=6) at drizzled/signal_handler.cc:98
#2 drizzled_handle_segfault (sig=6) at drizzled/signal_handler.cc:156
#3 <signal handler called>
#4 0x0000003b9de34085 in raise () from /lib64/libc.so.6
#5 0x0000003b9de35a36 in abort () from /lib64/libc.so.6
#6 0x0000003ba96bc08d in __gnu_cxx::__verbose_terminate_handler() ()
   from /usr/lib64/libstdc++.so.6
#7 0x0000003ba96ba2a6 in ?? () from /usr/lib64/libstdc++.so.6
#8 0x0000003ba96ba2d3 in std::terminate() () from /usr/lib64/libstdc++.so.6
#9 0x0000003ba96ba3de in __cxa_throw () from /usr/lib64/libstdc++.so.6
#10 0x00007f3f3d995f0e in ?? () from /usr/lib64/libboost_thread-mt.so.1.44.0
#11 0x00007f3f3d99888c in boost::thread::start_thread() ()
   from /usr/lib64/libboost_thread-mt.so.1.44.0
#12 0x00007f3f358f7e67 in thread<boost::_bi::bind_t<void, boost::_mfi::mf1<void, multi_thread::MultiThreadScheduler, long>, boost::_bi::list2<boost::_bi::value<multi_thread::MultiThreadScheduler*>, boost::_bi::value<long> > > > (
    this=0x1f61970, session=...)
    at /usr/include/boost/thread/detail/thread.hpp:204
#13 multi_thread::MultiThreadScheduler::addSession (this=0x1f61970,
    session=...) at plugin/multi_thread/multi_thread.cc:117
#14 0x000000000065b3dc in drizzled::Session::schedule (arg=...)
    at drizzled/session.cc:576
#15 0x000000000052c77f in main (argc=<value optimized out>,
    argv=<value optimized out>) at drizzled/main.cc:363

Related branches

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :
Changed in drizzle:
assignee: nobody → Andrew Hutchings (linuxjedi)
Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

OK, so what is happening is "ulimit -u" is getting hit, this is causing boost::thread_resource_error exception to be thrown. We need to catch this and change it to an error.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.