[MDEV-16458] Crash report Created: 2018-06-11  Updated: 2018-06-12  Resolved: 2018-06-11

Status: Closed
Project: MariaDB Server
Component/s: Optimizer
Affects Version/s: 10.3.7
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Pierre Assignee: Alice Sherepa
Resolution: Duplicate Votes: 0
Labels: crash
Environment:

Gentoo linux x64 (up to date) USE flags ="backup pam perl server tcmalloc xml" ABI_X86="(64)"

Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz
SGDB on Nvme x4 SSD soft raid, fs : ext4.
64Go RAM.
Connection : unix socket
Kernel (OVH kernel) : 4.11.4-xxxx-std-ipv6-64


Attachments: Text File crash_mysql_S4.txt    
Issue Links:
Duplicate
duplicates MDEV-15247 Crash when SET NAMES 'utf8' is set Closed

 Description   

I link a crash report, it append everytime I exec this kind of request.
Another query :
Query (0x5645a0188020): SELECT p.`id_product`, product_shop.`condition`, p.`id_manufacturer`, sa.`quantity`, p.`weight`

FROM cj_product p INNER JOIN cj_product_shop product_shop
ON (product_shop.id_product = p.id_product AND product_shop.id_shop = 1)

INNER JOIN cj_category_product cp ON (cp.id_product = p.id_product)
INNER JOIN cj_category c ON (c.id_category = cp.id_category AND
c.nleft >= 4
AND c.nright <= 5
AND c.active = 1) LEFT JOIN `cj_stock_available` sa
ON (sa.id_product = p.id_product AND sa.id_shop = 1)
WHERE product_shop.`active` = 1 AND product_shop.`visibility` IN ("both", "catalog") AND p.id_product IN (SELECT id_product FROM cj_feature_product fp WHERE fp.`id_feature_value` = 605) AND p.id_product IN (SELECT id_product FROM cj_feature_product fp WHERE fp.`id_feature_value` = 562 OR fp.`id_feature_value` = 558) AND p.id_product IN (SELECT id_product FROM cj_feature_product fp WHERE fp.`id_feature_value` = 338)
GROUP BY p.id_product

I can reproduce the bug by running it in PhpMyAdmin :
If I remove the LEFT here : "LEFT JOIN `cj_stock_available`". The query don't crash the server.
I repaired the table with
mysqlcheck -u USER -p --check -A --auto-repair
But same problem.



 Comments   
Comment by Alice Sherepa [ 2018-06-11 ]

Thanks for the report!
It looks like it is the same problem as MDEV-15247. I close it for now, but if the problem will appear after the version, where MDEV-15247 will be fixed, please write here and the case will be reopened

Comment by Pierre [ 2018-06-12 ]

Same without 'set names UTF8'.

But I forgot to show the storage engine : MyISAM.

All DB converted to innoDB, and no problem with innoDB.

Generated at Thu Feb 08 08:29:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.