× Heads up!

Aqua Data Studio / nhilam

IDE for Relational Databases
kin-hong reported 2015-06-14T01:37:53Z  · tariqrahiman last modified 2015-06-16T22:11:28Z

Result set pinning implementation may cause memory leak

Kin-Hong Wong
Tariq Rahiman
Priority Major
Complexity Unknown
Component Q Analyzer - Grid Results
Version 16.0

The current implementation of result set pinning may cause memory leak. To reproduce this:

  1. use the -Xmx678m memory setting to start ADS
  2. turn pinning off under File->Options
  3. open a query analyzer and connect to MySQL performance_schema
  4. note the memory usage readings on the bottom right of ADS
  5. execute the following query:
    1. SELECT * FROM events_waits_summary_by_account_by_event_name E, events_statements_summary_by_host_by_event_name F limit 50000
  6. note the memory used indicator on the bottom right of ADS
  7. execute the following query:
    1. SELECT null
  8. click the memory trashcan icon a few times
  9. notice that the memory usage readings did not revert to the readings in step 4.

In the pinning implementation, the ResultSetTableView instance in a query panel is not destroyed across multiple query executions, yet references to ResultSetTableModel were not cleaned up before the next query execution, resulting in memory leak of the previous ResultSetTableModel.

1 attachment

Issue #13366

Resolved 2015-06-16T19:39:14Z
No due date
Fixed Build 16.0.5-12, 17.0.0-dev-52
No time estimate

About AquaClusters Privacy Policy Support Version - 19.0.2-4 AquaFold, Inc Copyright © 2007-2017