[MDEV-15247] Crash when SET NAMES 'utf8' is set - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.2.12, 10.0(EOL), 10.1(EOL), 10.2(EOL)
Fix Version/s: 10.0.36, 10.1.35, 10.2.16, 10.3.8
Component/s: Optimizer
Labels:
- mariadb
Environment:
CentOS 7

Description

Simple select query that crashes MariaDB 10.2.
Crash does not happen when set names utf8 is not set.

SET NAMES 'utf8';

SELECT p.`id_product`, product_shop.`condition`, p.`id_manufacturer`, sa.`quantity`, p.`weight` , psi.price_min, psi.price_max

             FROM ps_product p  INNER JOIN ps_product_shop product_shop

                ON (product_shop.id_product = p.id_product AND product_shop.id_shop = 1)

             INNER JOIN ps_category_product cp ON (cp.id_product = p.id_product)

             INNER JOIN ps_category c ON (c.id_category = cp.id_category AND c.nleft >= 3 AND c.nright <= 24 AND c.active = 1)

             LEFT JOIN `ps_stock_available` sa ON (sa.id_product = p.id_product AND sa.id_shop = 1)

             INNER JOIN `ps_layered_price_index` psi ON (psi.id_product = p.id_product AND psi.id_currency = 1)

               WHERE product_shop.`active` = 1 AND product_shop.`visibility` IN ("both","catalog")  AND p.id_product IN

                (SELECT id_product FROM ps_feature_product fp WHERE fp.`id_feature_value` = 32)  AND p.id_product IN

                  (SELECT id_product FROM ps_feature_product fp WHERE fp.`id_feature_value` = 15)  AND p.id_product IN

                    (SELECT id_product FROM ps_feature_product fp WHERE fp.`id_feature_value` = 18 OR fp.`id_feature_value` = 19)  AND p.id_product IN

                      (SELECT id_product FROM ps_feature_product fp WHERE fp.`id_feature_value` = 34 OR fp.`id_feature_value` = 23)  AND p.id_product IN

                        (SELECT id_product FROM ps_feature_product fp WHERE fp.`id_feature_value` = 29 OR fp.`id_feature_value` = 28 OR fp.`id_feature_value` = 26)

             GROUP BY p.id_product;

Log:

Feb  8 10:26:19 uvn-234-24 mysqld: Version: '10.2.12-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server

Feb  8 10:26:19 uvn-234-24 systemd: Started MariaDB database server.

Feb  8 10:26:55 uvn-234-24 systemd: Started Session 1150 of user root.

Feb  8 10:26:55 uvn-234-24 systemd-logind: New session 1150 of user root.

Feb  8 10:26:55 uvn-234-24 systemd: Starting Session 1150 of user root.

Feb  8 10:26:55 uvn-234-24 systemd-logind: Removed session 1150.

Feb  8 10:28:31 uvn-234-24 mysqld: 180208 10:28:31 [ERROR] mysqld got signal 11 ;

Feb  8 10:28:31 uvn-234-24 mysqld: This could be because you hit a bug. It is also possible that this binary

Feb  8 10:28:31 uvn-234-24 mysqld: or one of the libraries it was linked against is corrupt, improperly built,

Feb  8 10:28:31 uvn-234-24 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.

Feb  8 10:28:31 uvn-234-24 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs

Feb  8 10:28:31 uvn-234-24 mysqld: We will try our best to scrape up some info that will hopefully help

Feb  8 10:28:31 uvn-234-24 mysqld: diagnose the problem, but since we have already crashed,

Feb  8 10:28:31 uvn-234-24 mysqld: something is definitely wrong and this may fail.

Feb  8 10:28:31 uvn-234-24 mysqld: Server version: 10.2.12-MariaDB

Feb  8 10:28:31 uvn-234-24 mysqld: key_buffer_size=134217728

Feb  8 10:28:31 uvn-234-24 mysqld: read_buffer_size=131072

Feb  8 10:28:31 uvn-234-24 mysqld: max_used_connections=1

Feb  8 10:28:31 uvn-234-24 mysqld: max_threads=153

Feb  8 10:28:31 uvn-234-24 mysqld: thread_count=7

Feb  8 10:28:31 uvn-234-24 mysqld: It is possible that mysqld could use up to

Feb  8 10:28:31 uvn-234-24 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467244 K  bytes of memory

Feb  8 10:28:31 uvn-234-24 mysqld: Hope that's ok; if not, decrease some variables in the equation.

Feb  8 10:28:31 uvn-234-24 mysqld: Thread pointer: 0x7fe6e9a04e38

Feb  8 10:28:31 uvn-234-24 mysqld: Attempting backtrace. You can use the following information to find out

Feb  8 10:28:31 uvn-234-24 mysqld: where mysqld died. If you see no messages after this, something went

Feb  8 10:28:31 uvn-234-24 mysqld: terribly wrong...

Feb  8 10:28:31 uvn-234-24 mysqld: stack_bottom = 0x7fe6d80c6d70 thread_stack 0x49000

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7fe6e6511c4e]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x7fe6e5f9c825]

Feb  8 10:28:31 uvn-234-24 mysqld: /lib64/libpthread.so.0(+0xf130)[0x7fe6e5501130]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_ZN10TABLE_LIST33is_with_table_recursive_referenceEv+0x0)[0x7fe6e5f2e4a0]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_ZN13st_join_table7cleanupEv+0x18)[0x7fe6e5e489d8]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_ZN4JOIN7cleanupEb+0x368)[0x7fe6e5e49058]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_ZN4JOIN9join_freeEv+0x4c)[0x7fe6e5e4934c]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_ZN4JOIN10exec_innerEv+0x9b5)[0x7fe6e5e60635]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_ZN4JOIN4execEv+0x33)[0x7fe6e5e608d3]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x11a)[0x7fe6e5e60a2a]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x254)[0x7fe6e5e61584]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(+0x415dcc)[0x7fe6e5d46dcc]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x6d85)[0x7fe6e5e113a5]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x2de)[0x7fe6e5e13a5e]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x209f)[0x7fe6e5e16a6f]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_Z10do_commandP3THD+0x149)[0x7fe6e5e17669]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1aa)[0x7fe6e5edaefa]

Feb  8 10:28:31 uvn-234-24 mysqld: /usr/sbin/mysqld(handle_one_connection+0x3d)[0x7fe6e5edb01d]

Feb  8 10:28:31 uvn-234-24 mysqld: /lib64/libpthread.so.0(+0x7df3)[0x7fe6e54f9df3]

Feb  8 10:28:31 uvn-234-24 mysqld: /lib64/libc.so.6(clone+0x6d)[0x7fe6e3b511ad]

Feb  8 10:28:31 uvn-234-24 mysqld: Trying to get some variables.

Feb  8 10:28:31 uvn-234-24 mysqld: Some pointers may be invalid and cause the dump to abort.

Feb  8 10:28:31 uvn-234-24 mysqld: Query (0x7fe6e9a12400): SELECT p.`id_product`, product_shop.`condition`, p.`id_manufacturer`, sa.`quantity`, p.`weight` , psi.price_min, psi.price_max              FROM ps_product p  INNER JOIN ps_product_shop product_shop                 ON (product_shop.id_product = p.id_product AND product_shop.id_shop = 1)              INNER JOIN ps_category_product cp ON (cp.id_product = p.id_product)              INNER JOIN ps_category c ON (c.id_category = cp.id_category AND c.nleft >= 3 AND c.nright <= 24 AND c.active = 1)              LEFT JOIN `ps_stock_available` sa ON (sa.id_product = p.id_product AND sa.id_shop = 1)               INNER JOIN `ps_layered_price_index` psi ON (psi.id_product = p.id_product AND psi.id_currency = 1)                 WHERE product_shop.`active` = 1 AND product_shop.`visibility` IN ("both","catalog")  AND p.id_product IN                 (SELECT id_product FROM ps_feature_product fp WHERE fp.`id_feature_value` = 32)  AND p.id_product IN                   (SELECT id_product FROM ps_feature_product fp WHERE fp.`id_feature_value` = 15)  AND p.id_product IN                     (SELECT id_product FROM ps_feature_product fp WHERE fp.`id_feature_value` = 18 OR fp.`id_feature_value` = 19)  AND p.id_product IN                        (SELECT id_product FROM ps_feature_product fp WHERE fp.`id_feature_value` = 34 OR fp.`id_feature_value` = 23)  AND p.id_product IN                         (SELECT id_product FROM ps_feature_product fp WHERE fp.`id_feature_value` = 29 OR fp.`id_feature_value` = 28 OR fp.`id_feature_value` = 26)               GROUP BY p.id_product

Feb  8 10:28:31 uvn-234-24 mysqld: Connection ID (thread ID): 10

Feb  8 10:28:31 uvn-234-24 mysqld: Status: NOT_KILLED

Feb  8 10:28:31 uvn-234-24 mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on

Feb  8 10:28:31 uvn-234-24 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

Feb  8 10:28:31 uvn-234-24 mysqld: information that should help you find out what is causing the crash.

Feb  8 10:28:31 uvn-234-24 systemd: mariadb.service: main process exited, code=killed, status=11/SEGV

Feb  8 10:28:31 uvn-234-24 systemd: Unit mariadb.service entered failed state.

Feb  8 10:28:31 uvn-234-24 systemd: mariadb.service failed.

Feb  8 10:28:36 uvn-234-24 systemd: mariadb.service holdoff time over, scheduling restart.

Feb  8 10:28:36 uvn-234-24 systemd: Starting MariaDB database server...

Attachments

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

dump.txt
78 kB
2018-02-08 08:38

Issue Links

is duplicated by

MDEV-15434 Mariadb crashes several times

Closed

MDEV-16458 Crash report

Closed

relates to

MDEV-16751 Server crashes in st_join_table::cleanup or TABLE_LIST::is_with_table_recursive_reference with join_cache_level>2

Closed

Activity

Ascending order - Click to sort in descending order

Silver Asu created issue - 2018-02-08 08:37

Silver Asu made changes - 2018-02-08 08:38

Field	Original Value	New Value
Attachment		dump.txt [ 45172 ]

Elena Stepanova made changes - 2018-02-10 01:26

Fix Version/s		10.2 [ 14601 ]
Assignee		Alice Sherepa [ alice ]

Elena Stepanova made changes - 2018-02-10 01:26

Status

Open [ 1 ]

Confirmed [ 10101 ]

Elena Stepanova made changes - 2018-02-10 01:45

Component/s		Optimizer [ 10200 ]
Fix Version/s		10.0 [ 16000 ]
Fix Version/s		10.1 [ 16100 ]
Affects Version/s		10.2 [ 14601 ]
Affects Version/s		10.0 [ 16000 ]
Affects Version/s		10.1 [ 16100 ]
Priority	Critical [ 2 ]	Major [ 3 ]

Alice Sherepa made changes - 2018-02-12 15:06

Assignee

Alice Sherepa [ alice ]

Igor Babaev [ igor ]

Alice Sherepa made changes - 2018-03-06 12:47

Link

This issue is duplicated by ~~MDEV-15434~~ [ ~~MDEV-15434~~ ]

Igor Babaev (Inactive) made changes - 2018-05-25 21:09

Status

Confirmed [ 10101 ]

In Progress [ 3 ]

Alice Sherepa made changes - 2018-05-28 19:26

Assignee

Igor Babaev [ igor ]

Varun Gupta [ varun ]

Varun Gupta (Inactive) made changes - 2018-06-09 08:03

Comment

[ Looks like another materialization bug.
If I run the query provided in description with the optimizer_switch='materialization=off ', then i don't see any crash. ]

Varun Gupta (Inactive) made changes - 2018-06-11 06:39

Assignee	Varun Gupta [ varun ]	Sergei Petrunia [ psergey ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Alice Sherepa made changes - 2018-06-11 12:06

Link

This issue is duplicated by ~~MDEV-16458~~ [ ~~MDEV-16458~~ ]

Sergei Petrunia made changes - 2018-06-15 14:21

Assignee	Sergei Petrunia [ psergey ]	Varun Gupta [ varun ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Varun Gupta (Inactive) made changes - 2018-06-19 21:08

Fix Version/s		10.0.36 [ 22916 ]
Fix Version/s		10.1.35 [ 23116 ]
Fix Version/s		10.2.16 [ 23110 ]
Fix Version/s		10.3.8 [ 23113 ]
Fix Version/s	10.2 [ 14601 ]
Fix Version/s	10.0 [ 16000 ]
Fix Version/s	10.1 [ 16100 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Alice Sherepa made changes - 2018-07-13 10:57

Link

This issue relates to ~~MDEV-16751~~ [ ~~MDEV-16751~~ ]

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

Workflow

MariaDB v3 [ 85489 ]

MariaDB v4 [ 153761 ]

People

Assignee:: Varun Gupta (Inactive)

Reporter:: Silver Asu

Votes:: 1 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: 2018-02-08 08:37

Updated:: 2018-07-13 10:57

Resolved:: 2018-06-19 21:08

Git Integration

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