Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL)
Description
Present in 10.5+ only, both in debug and optimized.
IF(NOT (scalar (@0s)>scalar (@0s))) { die (.);�ku u va�oj SQL sINTaksi{ die (. na liniji0;; |
SHUTDOWN;
|
Leads to (ref error log after shutdown):
11.0.1 f2dc4d4c10ac36a73b5c1eb765352d3aee808d66 (Debug) |
2023-02-18 14:22:07 0 [Note] /test/MD180223-mariadb-11.0.1-linux-x86_64-dbg/bin/mariadbd: Shutdown complete
|
Warning: Memory not freed: 280
|
In all affected versions.
No UBSAN/ASAN issues observed.
I tried to make this work under MTR for some time, but failed. AFAICS ftm, this issue can only be reproduced in a client, not in MTR, not even when using the CLI via MTR i.e. --start-and-exit.
As such, you will need to start mariadbd and then mariadb manually/directly to reproduce.
Attachments
Issue Links
- relates to
-
MDEV-26186 280 Bytes lost in mysys/array.c, mysys/hash.c, sql/sp.cc, sql/sp.cc, sql/item_create.cc, sql/item_create.cc, sql/sql_yacc.yy:10748 when using oracle sql_mode
- Closed
-
MDEV-31578 DECLARE CURSOR: "Memory not freed: 280 bytes lost" on syntax error
- Closed