#1530 Memory leak

Gerd Wagner — Mon, 18 Nov 2024 19:55:40 -0000

Fixed in our GIT repository. Will be available in future snapshots an versions.

Excerpt from change log:

'#1530 Memory leak: SQL result tabs were not garbage collect as long as their Session was open.
Note: When a result tab of an open Session gets garbage collected the following line appears is SQuirreL's logs:
...INFO ... Result tab finalized for open Session "<...>" with id=<...>

Memory leak

G.Dimitrov — Mon, 20 May 2024 12:39:55 -0000

Version 4.7.1, JDK jdk-17.0.9+9, application run w/ option : -Xmx640m

There is a memory leakage, here's an example:
0. Open application
1. Open Mysql session ( session content row limit : 10000 )
Used memory: 88mb; force GC: 29mb
2. open table : 10000 rows / 27 columns
Used memory: 172mb : force GC: 39mb
3. execute: select of 440k rows
Used memory: 578mb; force GC: 512mb
4. Close result tab
force GC: 447mb
5. select 100k rows
Used memory: 553
6. close result tab
force GC: 534 mb
7. select 440k rows
java.lang.OutOfMemoryError: Java heap space

In some cases, when trying GK to 'reduce' the memory used, the application freezes, for example:
- Used RAM 500MB - Execute 4 times "Select" which does not return the result (0 rows) in 4 Result Tabs ...

Recent changes to 1530: Memory leak

#1530 Memory leak

Memory leak