[TIMOB-2194] iOS: Contexts are not closed
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2011-12-22T17:00:17.000+0000 |
| Affected Version/s | Release 1.5.0 |
| Fix Version/s | Release 1.8.0.1 |
| Components | iOS |
| Labels | n/a |
| Reporter | Stephen Tramer |
| Assignee | Stephen Tramer |
| Created | 2011-04-15T03:13:11.000+0000 |
| Updated | 2017-03-02T22:49:31.000+0000 |
Description
Contexts are not currently closed. This is because there were a series of bugs involving contexts where closing a context would:
- Invalidate certain windows which were opened from inside a context which was then closed
- Closing a context could interact unfavorably with certain types of event listeners
Unfortunately I no longer have the specific bug #s for bugs caused by context shutdown so that context cleanup can be tested.
Context cleanup is an extremely important task and this should be considered a CRITICAL BUG.
Assigning to Blain for bookkeeping.
Claiming. This is related to a helpdesk issue involving memory management. Contexts have a death grip on all proxies and possibly their view contents.
This is actually untrue right now, but may have re-introduced a large number of bugs. See commit f5887ae, which cleans up contexts when they are no longer required (by closing windows).
Putting this one on the back burner. Instead what we're more interested in now is why contexts don't release objects that are clearly no longer in use. See brand new sister bug #2207.
Swapping back to new/future since technically this bug is fixed. We just need more accurate context management.
Bumping to 'medium' priority, since we do currently release contexts. We just need to do it more intelligently.
Invalidated by the majority of memory management work that we've performed over the last several releases. Also supplanted by the concept of moving to single-context.
Closing ticket as invalid.