Bug #18683 Events: memory leak in event scheduler
Submitted: 31 Mar 2006 11:17 Modified: 17 Sep 2006 5:52
Reporter: Sergei Golubchik Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Stored Routines Severity:S3 (Non-critical)
Version:5.1 OS:
Assigned to: Andrey Hristov CPU Architecture:Any

[31 Mar 2006 11:17] Sergei Golubchik 
Description:
Currently evex thread allocates lots of memory in evex memroot.
In particular it stores events there. But as an memroot cannot free memory,
when an event is destroyed (e.g. dropped), the memory becomes lost.
To free it one has to restart evex thread:

  set event_scheduler=0;
  set event_scheduler=1;

How to repeat:
 

Suggested fix:
for example, use malloc() for objects that are net persistent by nature.
[15 Sep 2006 13:10] Dmitry Lenev 
Fixed in 5.1.12
[17 Sep 2006 5:52] Jon Stephens 
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

Documented bugfix in 5.1.12 changelog.