Issues

Select view

Select search mode

 
36 of 36

Audit plugin "leaks" memory

Done

Description

Hello!

We see the audit plugin is causing growth of memory over time if threads remain connected for long. Memory IS released when thread disconnects, but many applications remain forever connected and the excess utilization becomes visible over the days.

Disabling audit plugins prevents memory growth. Here’s simple test case:

You can then monitor memory like:

 

Eventually the memory grows faster over time, as allocations appear to double at some point.

This resembles old bug for audit plugin:

And in performance schema we see that doubling in THD::Variables:

You can see initial growth takes some time, but again: over the days it just racks up gigabytes worth.

Environment

None

AFFECTED CS IDs

CS0048718

Details

Assignee

Reporter

Needs QA

Yes

In progress time

3.25

Time tracking

No time logged3d 2h remaining

Sprint

Affects versions

Priority

Smart Checklist

Created August 30, 2024 at 1:51 AM
Updated January 8, 2025 at 9:48 AM
Resolved October 1, 2024 at 6:03 PM

Activity

Show:

Oleksandr Kachan October 1, 2024 at 6:05 PM

Improved handling of table access events received in scope of one query. Previously plugin could fail to properly identify them which led to failure to clean internal data structures.

Loading...