Details
Description
SP/PS (Stored Procedures / Prepared Statements) allocates memory till the PS cache of SP will be destroyed. There is no way to see how many memory allocated and if it grows with each execution (first 2 execution can lead to new memory allocation but not more)
Task minimum:
Status variables which count the memory used/allocated for SP/PS by thread and/or for the server.
Other ideas:
- Automatic stop allocation in debugging version after second execution and call exception on attempt.
- Information schema by threads and SP/PS with information about allocated and used memory
Information can be collected in MEM_ROOTs of SP/PS. Storing info about status of mem_root before execution then checking after new allocated memory can be found.
MEM_ROOT can be changed to have debug mode which make it read only which can be switched on after second execution.
Attachments
Issue Links
- relates to
-
MDEV-30889 Memory leak issues with MariaDB 10.6.12 and OOM Crashes
-
- Needs Feedback
-
-
MDEV-32223 Memory leak showed in MDEV-6146 test suite
-
- In Review
-
-
MDEV-31127 Possible memory leak on running insert in PS mode against a table with a trigger that fires creation of a new partiton
-
- Open
-