[MDEV-8632] Segmentation fault on INSERT - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 5.3.12, 5.5.45, 10.0.21, 10.1.6
Fix Version/s: 5.5.47, 10.0.23, 10.1.9
Component/s: OTHER
Labels:
None
Environment:
Debian 7.8 (kernel=3.2.0-4-amd64), 16GB RAM
CentOS 7.1 (kernel=3.10.0-229.11.1.el7.x86_64), 8GB RAM

Sprint:
10.1.9-2

Description

I have got a segmentation fault error with query.
A client take a message - Error Code: 2013. Lost connection to MySQL server during query.

Query
insert into _tmp (id, r)
select id,p from
(
select id,
d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d as p
from (
select id, if(r=r,1,2) as d
from _tmp
) a
) b
on duplicate key update r=p;

Table _tmp has a structure:

CREATE TABLE `_tmp` (

  `id` int(10) unsigned NOT NULL,

  `r` float NOT NULL,

  PRIMARY KEY (`id`)

) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

But if simplify query the error will go away.
For example: replace one or more '+d' on '+1'
or replace 'r=r' on 'r=1'
or replace 'r=p' on 'r=1'.

The error is repeatable on MariaDB 5.5.45, 10.0.21, 10.1.6.
There is no error on Mysql 5.5 and 5.0.

Error log shows:

150817  4:15:17 [ERROR] mysqld got signal 11 ;

Server version: 10.1.6-MariaDB-1~wheezy-log

key_buffer_size=134217728

read_buffer_size=2097152

max_used_connections=3

max_threads=102

thread_count=2

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759823 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f333dbde008

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 = 0x7f3370172e30 thread_stack 0x48000

/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f3370cb658b]

/usr/sbin/mysqld(handle_fatal_signal+0x455)[0x7f337084de05]

/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f336fe3f0a0]

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0x7f335602d020): is an invalid pointer

Connection ID (thread ID): 5

Status: NOT_KILLED

------------------------------------------

Binary log mariadb-bin.000001 is in the private uploads.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

my.cnf
5 kB
2015-08-17 04:56

Activity

Ascending order - Click to sort in descending order

Konstantin created issue - 2015-08-17 04:50

Konstantin made changes - 2015-08-17 04:56

Field	Original Value	New Value
Attachment		my.cnf [ 39200 ]

Elena Stepanova made changes - 2015-08-18 02:02

Description

I have got a segmentation fault error with query.
A client take a message - Error Code: 2013. Lost connection to MySQL server during query.

Query:
{{insert into _tmp (id, r)
select id,p from
(
select id,
d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d as p
from (
select id, if(r=r,1,2) as d
from _tmp
) a
) b
on duplicate key update r=p;}}

Table _tmp has a structure:
{{CREATE TABLE `_tmp` (
  `id` int(10) unsigned NOT NULL,
  `r` float NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;}}

But if simplify query the error will go away.
For example: replace one or more '+d' on '+1'
or replace 'r=r' on 'r=1'
or replace 'r=p' on 'r=1'.

The error is repeatable on MariaDB 5.5.45, 10.0.21, 10.1.6.
There is no error on Mysql 5.5 and 5.0.

Error log shows:
150817 4:15:17 [ERROR] mysqld got signal 11 ;

Server version: 10.1.6-MariaDB-1~wheezy-log
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=3
max_threads=102
thread_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759823 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f333dbde008
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 = 0x7f3370172e30 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f3370cb658b]
/usr/sbin/mysqld(handle_fatal_signal+0x455)[0x7f337084de05]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f336fe3f0a0]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f335602d020): is an invalid pointer
Connection ID (thread ID): 5
Status: NOT_KILLED
------------------------------------------

Binary log mariadb-bin.000001 is in the private uploads.

I have got a segmentation fault error with query.
A client take a message - Error Code: 2013. Lost connection to MySQL server during query.

{code:sql|title=Query}
insert into _tmp (id, r)
select id,p from
(
select id,
d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d as p
from (
select id, if(r=r,1,2) as d
from _tmp
) a
) b
on duplicate key update r=p;}}
{code}

Table _tmp has a structure:
{code:sql}
CREATE TABLE `_tmp` (
  `id` int(10) unsigned NOT NULL,
  `r` float NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;}}
{code}

But if simplify query the error will go away.
For example: replace one or more {{'+d'}} on {{'+1'}}
or replace {{'r=r'}} on {{'r=1'}}
or replace {{'r=p'}} on {{'r=1'}}.

The error is repeatable on MariaDB 5.5.45, 10.0.21, 10.1.6.
There is no error on Mysql 5.5 and 5.0.

Error log shows:
{noformat}
150817 4:15:17 [ERROR] mysqld got signal 11 ;

Server version: 10.1.6-MariaDB-1~wheezy-log
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=3
max_threads=102
thread_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759823 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f333dbde008
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 = 0x7f3370172e30 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f3370cb658b]
/usr/sbin/mysqld(handle_fatal_signal+0x455)[0x7f337084de05]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f336fe3f0a0]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f335602d020): is an invalid pointer
Connection ID (thread ID): 5
Status: NOT_KILLED
{noformat}
------------------------------------------

Binary log mariadb-bin.000001 is in the private uploads.

Elena Stepanova made changes - 2015-08-18 02:03

Description

I have got a segmentation fault error with query.
A client take a message - Error Code: 2013. Lost connection to MySQL server during query.

{code:sql|title=Query}
insert into _tmp (id, r)
select id,p from
(
select id,
d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d as p
from (
select id, if(r=r,1,2) as d
from _tmp
) a
) b
on duplicate key update r=p;}}
{code}

Table _tmp has a structure:
{code:sql}
CREATE TABLE `_tmp` (
  `id` int(10) unsigned NOT NULL,
  `r` float NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
{code}

But if simplify query the error will go away.
For example: replace one or more {{'+d'}} on {{'+1'}}
or replace {{'r=r'}} on {{'r=1'}}
or replace {{'r=p'}} on {{'r=1'}}.

The error is repeatable on MariaDB 5.5.45, 10.0.21, 10.1.6.
There is no error on Mysql 5.5 and 5.0.

Error log shows:
{noformat}
150817 4:15:17 [ERROR] mysqld got signal 11 ;

Server version: 10.1.6-MariaDB-1~wheezy-log
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=3
max_threads=102
thread_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759823 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f333dbde008
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 = 0x7f3370172e30 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f3370cb658b]
/usr/sbin/mysqld(handle_fatal_signal+0x455)[0x7f337084de05]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f336fe3f0a0]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f335602d020): is an invalid pointer
Connection ID (thread ID): 5
Status: NOT_KILLED
{noformat}
------------------------------------------

Binary log mariadb-bin.000001 is in the private uploads.

Elena Stepanova made changes - 2015-08-18 02:04

Description

I have got a segmentation fault error with query.
A client take a message - Error Code: 2013. Lost connection to MySQL server during query.

{code:sql|title=Query}
insert into _tmp (id, r)
select id,p from
(
select id,
d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d as p
from (
select id, if(r=r,1,2) as d
from _tmp
) a
) b
on duplicate key update r=p;}}
{code}

Table _tmp has a structure:
{code:sql}
CREATE TABLE `_tmp` (
  `id` int(10) unsigned NOT NULL,
  `r` float NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
{code}

But if simplify query the error will go away.
For example: replace one or more {{'+d'}} on {{'+1'}}
or replace {{'r=r'}} on {{'r=1'}}
or replace {{'r=p'}} on {{'r=1'}}.

The error is repeatable on MariaDB 5.5.45, 10.0.21, 10.1.6.
There is no error on Mysql 5.5 and 5.0.

Error log shows:
{noformat}
150817 4:15:17 [ERROR] mysqld got signal 11 ;

Server version: 10.1.6-MariaDB-1~wheezy-log
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=3
max_threads=102
thread_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759823 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f333dbde008
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 = 0x7f3370172e30 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f3370cb658b]
/usr/sbin/mysqld(handle_fatal_signal+0x455)[0x7f337084de05]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f336fe3f0a0]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f335602d020): is an invalid pointer
Connection ID (thread ID): 5
Status: NOT_KILLED
{noformat}
------------------------------------------

Binary log mariadb-bin.000001 is in the private uploads.

I have got a segmentation fault error with query.
A client take a message - Error Code: 2013. Lost connection to MySQL server during query.

{code:sql|title=Query}
insert into _tmp (id, r)
select id,p from
(
  select id,
  d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d+d as p
  from (
    select id, if(r=r,1,2) as d
    from _tmp
  ) a
) b
on duplicate key update r=p;
{code}

Table _tmp has a structure:
{code:sql}
CREATE TABLE `_tmp` (
  `id` int(10) unsigned NOT NULL,
  `r` float NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
{code}

But if simplify query the error will go away.
For example: replace one or more {{'+d'}} on {{'+1'}}
or replace {{'r=r'}} on {{'r=1'}}
or replace {{'r=p'}} on {{'r=1'}}.

The error is repeatable on MariaDB 5.5.45, 10.0.21, 10.1.6.
There is no error on Mysql 5.5 and 5.0.

Error log shows:
{noformat}
150817 4:15:17 [ERROR] mysqld got signal 11 ;

Server version: 10.1.6-MariaDB-1~wheezy-log
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=3
max_threads=102
thread_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759823 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f333dbde008
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 = 0x7f3370172e30 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f3370cb658b]
/usr/sbin/mysqld(handle_fatal_signal+0x455)[0x7f337084de05]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f336fe3f0a0]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f335602d020): is an invalid pointer
Connection ID (thread ID): 5
Status: NOT_KILLED
{noformat}
------------------------------------------

Binary log mariadb-bin.000001 is in the private uploads.

Elena Stepanova made changes - 2015-08-18 02:06

Status

Open [ 1 ]

Confirmed [ 10101 ]

Elena Stepanova made changes - 2015-08-18 02:06

Component/s		Optimizer [ 10200 ]
Component/s	Data Manipulation - Insert Delayed [ 10101 ]

Elena Stepanova made changes - 2015-08-18 02:07

Affects Version/s

5.3.12 [ 12000 ]

Elena Stepanova made changes - 2015-08-18 02:11

Fix Version/s		10.1 [ 16100 ]
Fix Version/s		10.0 [ 16000 ]
Fix Version/s		5.5 [ 15800 ]
Assignee		Oleksandr Byelkin [ sanja ]

Rasmus Johansson (Inactive) made changes - 2015-11-04 10:52

Sprint

10.1.9-2 [ 19 ]

Rasmus Johansson (Inactive) made changes - 2015-11-04 10:52

Rank

Ranked lower

Oleksandr Byelkin made changes - 2015-11-04 18:48

Status

Confirmed [ 10101 ]

In Progress [ 3 ]

Oleksandr Byelkin made changes - 2015-11-09 09:29

Assignee	Oleksandr Byelkin [ sanja ]	Sergey Vojtovich [ svoj ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Sergey Vojtovich made changes - 2015-11-09 15:56

Assignee	Sergey Vojtovich [ svoj ]	Oleksandr Byelkin [ sanja ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Oleksandr Byelkin made changes - 2015-11-09 17:19

Component/s		OTHER [ 10125 ]
Component/s	Optimizer [ 10200 ]
Fix Version/s		10.0.23 [ 20401 ]
Fix Version/s		10.1.9 [ 20301 ]
Fix Version/s		5.5.47 [ 20300 ]
Fix Version/s	5.5 [ 15800 ]
Fix Version/s	10.0 [ 16000 ]
Fix Version/s	10.1 [ 16100 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Sergei Golubchik made changes - 2021-12-06 21:41

Workflow

MariaDB v3 [ 71100 ]

MariaDB v4 [ 149482 ]

People

Assignee:: Oleksandr Byelkin

Reporter:: Konstantin

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2015-08-17 04:50

Updated:: 2015-11-09 17:19

Resolved:: 2015-11-09 17:19

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Attachments

Activity

People

Dates

Git Integration