[TRINIDAD-1712] Memory Leaks in Trinidad table component

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 1.2.9-core
• Fix Version/s: 1.2.10-core
• Component/s: Components
• Environment: Red Hat Linux, JBOSS 4.2, Seam 2.0.x
• Assignee: Unassigned
• Reporter: Wolfgang Chico Toepfer
• Created: 08/Feb/10 14:44
• Updated: 13/Apr/10 07:37
• Resolved: 13/Apr/10 07:37

Description

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.