[
https://issues.apache.org/jira/browse/TRINIDAD-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-1712.
------------------------------------------
Fix Version/s: 1.2.10-core
Resolution: Duplicate
with https://issues.apache.org/jira/browse/TRINIDAD-1086 some improvements have
been made
> Memory Leaks in Trinidad table component
> ----------------------------------------
>
> Key: TRINIDAD-1712
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1712
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.2.9-core
> Environment: Red Hat Linux, JBOSS 4.2, Seam 2.0.x
> Reporter: Wolfgang Chico Toepfer
> Priority: Critical
> Fix For: 1.2.10-core
>
> Attachments: SeamidadTableMemoryLeaksMin.zip
>
>
> Unfortunately I could not upload a simple test application due to its size
> (no maven applied..) but I could eventually if the size of >10 MB is allowed.
> Anyway a test application can be easily built in principle because it's just
> a matter of repeatedly displaying a Trinidad table and checking back in a
> profiler that its internal data are not released i.e. precisely speaking,
> SortableModel and RowKeySetImpl.
> These two keep growing the following way: 1 instance of SortableModel per
> table and 2 instances of RowKeySetImpl per table.
> So the leak growth follows the scheme 1/2, 2/4, 3/6, 4/8 and so on.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
