> -----Original Message----- > From: Maria-developers [mailto:maria-developers- > [email protected]] On Behalf Of Roberto > Spadim > Sent: Montag, 16. September 2013 02:49 > To: [email protected] > Subject: [Maria-developers] BUG? at windows versino of mariadb 10.0.4
Yes, this is a bug, thus no need for a question mark - I would be seriously surprised if we would classify crash as a feature ;) I was not able to reproduce it myself, following your description . If you're able to reproduce it, please create a bug in JIRA. IF you're not able to get it on more than one machine, please start your server with --core-file, rerun the sequence that leads to the crash, and attach mysqld.dmp from the data directory to the bug report. To me it is not obvious why thread pool would affect Innodb background threads in any way (Innodb background threads are not in the pool). Also, just starting N connection and doing nothing (this is what your description sounds like) would not cause any activity in Innodb background threads, thus it should not lead to crash you describe. It seems to me that something crucial missing in your description, something that would make your crash reproducible . > Hi guys, i was trying the mariadb with lower value of > thread_pool_max_threads to 3 > and after my fourth connection i got a error and server crashed, it's > a new server, i downloaded the 32bits version of mariadb, unziped and > run this command line: > > C:\Program Files\mariadb-10.0.4-win32\bin>mysqld --datadir=..\data\ > --log_error=..\log --port=3306 --thread_pool_max_threads=3 > > the error output at log was: > 130915 21:43:37 [ERROR] mysqld got exception 0x80000003 ; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked against is corrupt, improperly built, > or misconfigured. This error can also be caused by malfunctioning hardware. > > To report this bug, see http://kb.askmonty.org/en/reporting-bugs > > We will try our best to scrape up some info that will hopefully help > diagnose the problem, but since we have already crashed, > something is definitely wrong and this may fail. > > Server version: 10.0.4-MariaDB > key_buffer_size=134217728 > read_buffer_size=131072 > max_used_connections=0 > max_threads=4 > thread_count=0 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = > 141750 K bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > Thread pointer: 0x0x0 > Attempting backtrace. You can use the following information to find out > where mysqld died. If you see no messages after this, something went > terribly wrong... > mysqld.exe!os_aio_windows_handle()[os0file.cc:4786] > mysqld.exe!fil_aio_wait()[fil0fil.cc:5396] > mysqld.exe!io_handler_thread()[srv0start.cc:477] > kernel32.dll!BaseThreadInitThunk() > ntdll.dll!RtlInitializeExceptionChain() > ntdll.dll!RtlInitializeExceptionChain() > The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains > information that should help you find out what is causing the crash. > > > > any help is wellcome, maybe the max_threads is bigger than > thread_pool_max_threads? that's could be the problem? i didn't checked > the source yet > > -- > Roberto Spadim > SPAEmpresarial > > _______________________________________________ > Mailing list: https://launchpad.net/~maria-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~maria-developers > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
