Bug #51149 | Command.TrimSemicolons uses a lot of memory | ||
---|---|---|---|
Submitted: | 12 Feb 2010 15:21 | Modified: | 17 Feb 2010 16:06 |
Reporter: | Simen Endsjø Haugen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / NET | Severity: | S5 (Performance) |
Version: | 6.2.2 (and 61.2,3 at least) | OS: | Any |
Assigned to: | Reggie Burnett | CPU Architecture: | Any |
Tags: | out of memory, StringBuilder, TrimSemicolons |
[12 Feb 2010 15:21]
Simen Endsjø Haugen
[12 Feb 2010 17:16]
Tonci Grgin
Hi Simen and thanks for your report. Verified as described by looking into latest sources.
[15 Feb 2010 20:36]
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/100438 792 Reggie Burnett 2010-02-15 - small performance fix (bug #51149)
[15 Feb 2010 20:37]
Reggie Burnett
fixed in 6.0.6, 6.1.4, 6.2.3, and 6.3.1+
[17 Feb 2010 16:06]
Tony Bedford
An entry has been added to changelogs for 6.0.6, 6.1.4, 6.2.3, 6.3.1: The method Command.TrimSemicolons used StringBuilder, and therefore allocated memory for the query even if it did not need to be trimmed. This led to excessive memory consumption when executing a number of large queries.