leak.png
[MXS-2046] Memory leak in binlog router Created: 2018-09-12 Updated: 2020-08-25 Resolved: 2019-05-09 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | binlogrouter |
| Affects Version/s: | 2.2.13 |
| Fix Version/s: | 2.3.7 |
| Type: | Bug | Priority: | Major |
| Reporter: | Hartmut Holzgraefe | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
leak.png
|
| Description |
|
A maxscale instance with three binlog router services configured shows memory usage going up at a steady rate, eventually leading to an OOM-kill. Then after restart the new instance continues to grow at about the same rate. |
| Comments |
| Comment by markus makela [ 2018-09-12 ] |
|
Found a memory leak that happens when a client connects to the binlogrouter. |
| Comment by markus makela [ 2018-09-13 ] |
|
The memory is now correctly freed. |
| Comment by Johan Wikman [ 2019-05-09 ] |
|
Reopened as there seems to be a better candidate for the seen behaviour. BLR keeps registering a housekeeper callback over and over again, which will appear as if memory was being leaked. |
| Comment by Johan Wikman [ 2019-05-09 ] |
|
Fixed by |