[MCOL-441] Segfault on query after an error Created: 2016-12-05  Updated: 2016-12-09  Resolved: 2016-12-09

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.6

Type: Bug Priority: Critical
Reporter: Andrew Hutchings (Inactive) Assignee: David Hill (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
is caused by MCOL-424 cross engine subquery losing where cl... Closed
Sprint: 2016-23, 2016-24

 Description   

The fix for MCOL-424 adds index_hints to thd->mem_root. On a bad query thd->mem_root is freed but the pointers remain. Causing a segfault on the next query.

There are likely other ways to trigger this and it doesn't crash every time.

 Comments   
Comment by Andrew Hutchings (Inactive) [ 2016-12-05 ]

Only way I've been able to trigger the problem is using:

working_tpch1_compareLogOnly/storedProcedures/sp_autoswitch.sql

And running this query from it twice:

call sp_unstructured_loop(2)

I've tested this against the MCOL-424 case and that is still fixed.

Comment by Andrew Hutchings (Inactive) [ 2016-12-05 ]

Still problems

Comment by Andrew Hutchings (Inactive) [ 2016-12-05 ]

New version lets the regression suite pass

Comment by David Hill (Inactive) [ 2016-12-09 ]

passed regression test with now crashes...

Generated at Thu Feb 08 02:21:06 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.