Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
5.5(EOL), 10.0(EOL), 10.1(EOL)
-
Linux Debian 8 64 bits
LAMP server (web development server)
2cpu/4Go ram
mariaDB packages (rom mariaDB apt repository)
ii libmariadbclient18 10.1.9+maria-1~jessie amd64 MariaDB database client library
ii mariadb-client-10.1 10.1.9+maria-1~jessie amd64 MariaDB database client binaries
ii mariadb-client-core-10.1 10.1.9+maria-1~jessie amd64 MariaDB database core client binaries
ii mariadb-common 10.1.9+maria-1~jessie all MariaDB database common files (e.g. /etc/mysql/conf.d/mariadb.cnf)
ii mariadb-server-10.1 10.1.9+maria-1~jessie amd64 MariaDB database server binaries
ii mariadb-server-core-10.1 10.1.9+maria-1~jessie amd64 MariaDB database core server files
Linux Debian 8 64 bits LAMP server (web development server) 2cpu/4Go ram mariaDB packages (rom mariaDB apt repository) ii libmariadbclient18 10.1.9+maria-1~jessie amd64 MariaDB database client library ii mariadb-client-10.1 10.1.9+maria-1~jessie amd64 MariaDB database client binaries ii mariadb-client-core-10.1 10.1.9+maria-1~jessie amd64 MariaDB database core client binaries ii mariadb-common 10.1.9+maria-1~jessie all MariaDB database common files (e.g. /etc/mysql/conf.d/mariadb.cnf) ii mariadb-server-10.1 10.1.9+maria-1~jessie amd64 MariaDB database server binaries ii mariadb-server-core-10.1 10.1.9+maria-1~jessie amd64 MariaDB database core server files
-
10.1.11, 5.5.48-0, 5.5.50, 5.5.51 & 10.2.2
Description
When we run a specific query, it makes MariaDb crash
Dec 16 18:14:48 wdevl01 mysqld: Some pointers may be invalid and cause the dump to abort.
|
Dec 16 18:14:48 wdevl01 mysqld: Query (0x32b8fc9d020): is an invalid pointer
|
Dec 16 18:14:48 wdevl01 mysqld: Connection ID (thread ID): 543
|
Dec 16 18:14:48 wdevl01 mysqld: Status: NOT_KILLED
|
We tested the query on MariaDB 10.0.22 and 10.1.9 and both crash the same way.
Executing the query using PHP or direct via myqsl CLI result in a crash.
Running the exact same query on the same imported database on Mysql 5.5.46 doesn't crash.
The query and full logs are in the attached mariadb_query_logs.txt. A database dump with relevant tables to reproduce the crash is provided with database_dump.zip.
Trying different mariadb configurations (buffer, etc) did not have an impact on the issue.
Switching back to the default debian config with slight changes result in a crash too (current mariadb config is also attached)
I checked the opened bugs and did not find one similar to this one.
Feel of course free to ask for more info if needed and btw, thanks for your work !
Sébastien Fiquemont - Ciméos
Attachments
Issue Links
Activity
cvicentiu, can you also check the original testcase? AFAIU we were working with the "Highly reduced test case derived from the initial one" made by Elena... Let's also check the original one...
cvicentiu, psergey, please check if MDEV-9513 is the same or different issue. It does not get fixed by this patch.
cvicentiu, psergey, please check if MDEV-9514 is related to this issue. It does not get fixed by this patch.
I haven't got any memory leaks so far, but my testing is limited due to the problems mentioned above. Could you please check if they are supposed to be fixed in the scope of this bug?
After discussing with Sergey Petrunia, we've come up with a fix that makes the crash go away, but we are not confident that it does not break anything else. The patch might introduce memory leaks. elenst after the buildbot here http://buildbot.askmonty.org/buildbot/grid?category=main&branch=bb-10.1-mdev-9304 finishes checking, can you run a valgrind suite with some randomly generated queries using UNION?