Bug #17610 ndbapi: dropEventOperation leaves object behind, memleak
Submitted: 21 Feb 2006 11:08 Modified: 19 May 2006 23:17
Reporter: Tomas Ulin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version: OS:
Assigned to: Tomas Ulin CPU Architecture:Any

[21 Feb 2006 11:08] Tomas Ulin 
Description:
dropEventOperation leaves object behind, memleak

How to repeat:
dropEventOperation leaves object behind, memleak
[18 May 2006 19:46] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/6593
[19 May 2006 21:33] Tomas Ulin 
reviewed by pekka
[19 May 2006 21:33] Tomas Ulin 
pushed to 5.1.11
[19 May 2006 23:17] 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 bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented fix in 5.1.11 changelog.