Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
2.3.16, 2.4.8
-
MXS-SPRINT-104, MXS-SPRINT-105
Description
Memory usage of a maxscale instance stayed low for a little less than 24 hours, then went up to about 4GB quickly within a span of ~30 minutes:
mem1.png shows the memory useage over a full after start, mem2.png the incline over the critical 30min period (note: x axis is in minutes, and y axis in kilobytes, don't let that confuse you)
This was originally reported against 2.3.9, which had some known leaks, but still seems to happen after upgrade to 2.3.16 (graphs are from 2.3.9)
Attachments
Issue Links
- relates to
-
MXS-2917 qc_sqlite leaks memory with complex CREATE TABLE query
-
- Closed
-