Bug #79068 Assertion failure in sync0arr.c during shutdown
Submitted: 2 Nov 2015 10:29 Modified: 23 Mar 2:58
Reporter: Stefan Zedeth Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:mysql Ver 14.14 Distrib 5.5.44 OS:Debian (armv7l)
Assigned to: CPU Architecture:Any
Tags: assertion failure, memory trapb, sync0arr.c

[2 Nov 2015 10:29] Stefan Zedeth
Description:
MySQL crashes during shutdown with an assertion failure generating a memory trap and leaving me puzzled:

[...]
151101 16:42:43 [Note] /usr/sbin/mysqld: Normal shutdown
151101 16:42:43 [Note] Event Scheduler: Purging the queue. 0 events
151101 16:42:43  InnoDB: Starting shutdown...
151101 16:42:45  InnoDB: Assertion failure in thread 1722807376 in file sync0arr.c line 317
InnoDB: Failing assertion: count == arr->n_reserved
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:42:45 UTC - mysqld got signal 6 ;
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.
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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=1
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346093 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x30000
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.
151101 16:42:45 mysqld_safe Number of processes running now: 0
151101 16:42:45 mysqld_safe mysqld restarted
[...]

How to repeat:
Only Owncloud 8.2.0 uses MySQL databases on the server.
Crash happens rarely during shutdown. Currently I unfortunately cannot say more about repeating steps.
[23 Feb 2:58] Miguel Solorzano
Sorry for the delay. It's still happens with latest releases version?. Thanks.
[24 Mar 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".