Details

    • 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
    • Labels:
      None
    • Environment:
      Red Hat Linux, JBOSS 4.2, Seam 2.0.x

      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.

        Attachments

        1. SeamidadTableMemoryLeaksMin.zip
          171 kB
          Wolfgang Chico Toepfer

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              wchico Wolfgang Chico Toepfer
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: