My Oracle Support Banner

Memory Leak In 5.7.21 - 5.7.24 When Using GET_LOCK() Function (Doc ID 2466685.1)

Last updated on MARCH 13, 2019

Applies to:

MySQL Server - Version 5.7 and later
Information in this document applies to any platform.

Symptoms

Specific versions of mysqld 5.7.21, 5.7.22, 5.7.23, 5.7.24 consume more and more memory over time.

Monitoring the memory usage using performance_schema reveals the leaks as follows:

/*!50700 select * from performance_schema.memory_summary_global_by_event_name where event_name in('memory/mysys/lf_node','memory/sql/User_level_lock','memory/mysys/lf_slist','memory/mysys/lf_dynarray')*/;

 https://dev.mysql.com/doc/refman/en/memory-summary-tables.html

Changes

 Server was recently upgraded to 5.7.21, 5.7.22, 5.7.23, or  5.7.24, AND there are many concurrent queries containing GET_LOCK function calls with zero timeout.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
 Workaround
 Permanent solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.