Details

      Description

      {html}<div><p>KrollObject appears to retain itself twice within its own
      constructor. This is an issue because quite often these objects are
      meant to be autoreleased - they never will be, unless this is
      resolved.</p>
      <p>From <a href="/projects/32238/tickets/2299" title=
      "Ticket #2299">#2299</a>:</p>
      <blockquote>
      <p>Bumping this down the road, with a note. It's two-pronged: Proxy
      retention issues (how we handle memory warnings is not smart right
      now, because it LEADS to memory warnings) and problems in Kroll
      involving certain objects which should be autoreleased (but never
      are, because they're retained at very bad points in their
      lifecycle). Unfortunately at this time there's no good way to
      handle clearing out stale client responses, simply because there's
      no good way to tell when they're "stale."<br>
      This bug should be a high priority target for a 1.5.1 release due
      to its critical nature.</p>
      </blockquote></div>{html}

        Attachments

          Activity

            People

            • Assignee:
              blainhamon Blain Hamon
              Reporter:
              stephentramer Stephen Tramer
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Backbone Issue Sync

                • Titanium SDK/CLI <> Titanium Mobile
                  Synced with:
                  TIMOB-2283
                  Sync status:
                  ERROR
                  Last received:
                  Last sent:

                  Git Integration