Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: Release 8.0.0, Release 8.0.1
    • Fix Version/s: Release 8.2.1
    • Component/s: iOS
    • Labels:
      None
    • Environment:
    • Story Points:
      8
    • Sprint:
      2019 Sprint 17, 2019 Sprint 18, 2019 Sprint 19, 2019 Sprint 20, 2019 Sprint 21

      Description

      Old table row references are not cleared when calling tableView.setData(rows).

      In a production app running SDK 7.4.1.GA this is causing serious memory issues. Because the row structure is quite complex, it's important that old rows are completely cleaned from memory before new ones are set.

      We've been able to reproduce this issue in a example application for multiple SDK's (8.0.0.GA, 7.4.1.GA, 8.0.1.GA). As demonstrated in the attached video you can see that the objects are not cleared from memory. The source code for the app running in the video has also been attached to this issue.

      We've tried calling `$.off();$.destroy();` on the `controllers/imagerow` controller, this does not destroy the proxies.

        Attachments

        1. app.zip
          8.05 MB
        2. Findings for TIMOB-27207.pdf
          67 kB
        3. invalid-references.mov
          1.31 MB
        4. memleak8.0.2.GA.mp4
          346 kB
        5. Memory Leak Monitoring.mov
          6.38 MB

          Activity

            People

            • Assignee:
              jvennemann Jan Vennemann
              Reporter:
              menzo VDLP
              Reviewer:
              Christopher Williams
            • Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Backbone Issue Sync

                • Backbone Issue Sync is enabled for your project, but we do not have any synchronization info for this issue.

                  Git Source Code