← Back to team overview

maria-discuss team mailing list archive

Re: MariaDB 10.1.15 Released and Crash


Hi Alex,

On 07/02/2016 01:35 PM, Alex wrote:
Hi Elena,

I had to downgrade and went back to 10.1.14 which doesn't cause any
problems. I may try to upgrade again tonight and turn on the general log.

Thanks, it won't be needed just yet, I think I have a test case for what you've encountered; but when the bug is fixed, maybe you'll want to try the patch and see if it really solves the problem on your side.



On 7/2/2016 1:24 PM, Elena Stepanova wrote:
Hi Alex,

On 07/02/2016 11:18 AM, Alex wrote:

Last night one of my servers updated MariaDB to 10.1.15 and it started
to crash every few minutes since the update ( from 10.1.14 -> 10.1.15 ).

Sorry about that. I assume you'll want to downgrade, but before you do
that, could you please enable the general log and check which query it
crashes on? It will be the last query from the connection ID which is
mentioned in the crash log (xxx):

Some pointers may be invalid and cause the dump to abort.
Query (0x7f5aaf1b5020): is an invalid pointer
Connection ID (thread ID): xxx

We have an open report with a stack trace similar to the visible part
of yours, https://jira.mariadb.org/browse/MDEV-7865. As the
description says, on some reason the scenario in the bug report didn't
cause the crash on 10.x (I just re-checked, still does not, and no
valgrind warnings either); but it's quite possible that the problem is
there anyway. Maybe with your query we'll be able to create a test
case for 10.x -- or maybe it's an entirely different bug, in which
case a JIRA report will be needed.



160702 10:22:13 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this
or one of the libraries it was linked against is corrupt, improperly
or misconfigured. This error can also be caused by malfunctioning

To report this bug, see https://mariadb.com/kb/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.1.15-MariaDB
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
1804821 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f5a89876008
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...
stack_bottom = 0x7f5ab5dd9058 thread_stack 0x48400







Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f5aaf1b5020): is an invalid pointer
Connection ID (thread ID): 456

Optimizer switch:


Anyone else encountered crashes on 10.1.15 ?

Mailing list: https://launchpad.net/~maria-discuss
Post to     : maria-discuss@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~maria-discuss
More help   : https://help.launchpad.net/ListHelp