Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
11.4.2
-
None
-
MariaDB version 11.4.2 on Win64
Description
I notice high RAM consumption after single action in HeidiSQL. After startup MariaDB service takes ~380 MB in RAM. Then It keeps same amount of memory for hours. Then I connect to DB using HeidiSQL and click to expand Views branch in tree component.
I can see command executed displayed:
SELECT `DEFAULT_COLLATION_NAME` FROM `information_schema`.`SCHEMATA` WHERE `SCHEMA_NAME`='mydb'; |
SHOW TABLE STATUS FROM `mydb`; |
SHOW FUNCTION STATUS WHERE `Db`='mydb'; |
SHOW PROCEDURE STATUS WHERE `Db`='mydb'; |
SHOW TRIGGERS FROM `mydb`; |
SELECT *, EVENT_SCHEMA AS `Db`, EVENT_NAME AS `Name` FROM information_schema.`EVENTS` WHERE `EVENT_SCHEMA`='mydb'; |
At that point mysqld.exe process takes 2749 MB RAM. Then I disconnect DB in HeidiSQL first and close the program itself. The server process keeps holding 2749 MB RAM.
Is that normal? How can I investigate memory issues? Can I force to release RAM without restarting service?
MariaDB version 11.4.2 on Win64.
Attachments
Issue Links
- relates to
-
MDEV-34912 THD may not cleaning up all memory between queries
- Open
-
MDEV-20699 mysqldump of routines causes MariaDB to get killed by oom-killer
- Closed