[MDEV-31257] Crash/signal 11 when running specific SQL query after update to 10.6.13 Created: 2023-05-12 Updated: 2023-05-16 Resolved: 2023-05-16 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Optimizer |
| Affects Version/s: | 10.6.13 |
| Fix Version/s: | 11.0.2, 10.4.30, 10.5.21, 10.6.14, 10.9.7, 10.11.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Brad | Assignee: | Sergei Petrunia |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Centos 7 |
||
| Attachments: |
|
| Description |
|
Our client noticed a problem with a cron job in their site after the 10.6.13 update. Looking into the issue, I found that a specific SQL query is causing the problem. For now, I've downgraded this server to 10.6.12 and it's working fine again. I've attached the log messages that happen during the event. I can reproduce the problem easily so if I need to get more information, let me know. Here is the SQL command that triggers the crash.
Any ideas what could be causing this? Thanks! |
| Comments |
| Comment by Elena Stepanova [ 2023-05-12 ] | |||||||
|
This looks like | |||||||
| Comment by Won Kyu Jeong [ 2023-05-12 ] | |||||||
|
I have a similar issue after upgrading to 10.10.4 from 10.10.3. | |||||||
| Comment by Brad [ 2023-05-12 ] | |||||||
|
I can't comment on the fix but I think it should be based on what I'm reading in the other tickets. Downgrading isn't that hard but could be different on your system. For me, I ran the following to downgrade to the previous release and lock the version for now (don't forget to undo this later).
You can unlock and update later like this:
| |||||||
| Comment by Sergei Petrunia [ 2023-05-16 ] | |||||||
|
Yes, the stack trace points at
(One can't see the crashing subquery in query text because it's inside a view) But the stack trace in this case is unique enough to point at | |||||||
| Comment by Sergei Petrunia [ 2023-05-16 ] | |||||||
|
Closing as duplicate of |