[MXS-3908] MaxScale crashes (double free or corruption) Created: 2021-12-09  Updated: 2021-12-10  Resolved: 2021-12-10

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 6.2.0
Fix Version/s: 6.2.1

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

XPand 5.3.18


 Description   

MaxScale seems to crash due to memory corruption:

2021-12-08 21:47:48   alert  : (Xpand-Read-Write-Split-Service); MaxScale 6.2.0 received fatal signal 11. Commit ID: e5f5c8a4cfb15b2ad1c76bad3599cd59332198e6 System name: Linux Release string: NAME="CentOS Linux"
 
2021-12-08 21:47:48   alert  : (Xpand-Read-Write-Split-Service); Statement currently being classified: none/unknown
 
double free or corruption (out)

Unfortunately it didn't produce a stacktrace which makes it harder to figure out where this happened.

 Comments   
Comment by markus makela [ 2021-12-10 ]

Managed to reproduce this once I reproduced MXS-3907. Seems that this was the result of MaxScale being too confused to do the right thing which resulted in std::deque::pop_back() being called with no contents in it. The fix to MXS-3907 also fixes this.

Comment by markus makela [ 2021-12-10 ]

Fixed by the same fix that fixes MXS-3907.

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