[MGNLUI-1673] PulseMessagePresenter creating a proper MessageListener introduces a MemoryLeak Created: 14/Jun/13 Updated: 14/Jun/13 Resolved: 14/Jun/13 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.0 |
| Type: | Task | Priority: | Blocker |
| Reporter: | Daniel Lipp | Assignee: | Daniel Lipp |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Sprint: | RC 2 |
| Description |
|
Stress-tests revealed we have a potential memory leak. When profiling we found even after logout we have always one AdmincentralUI instance around - together with all it's references. The problem is that in PulseMessagePresenter a proper MessageListener is created that's added to the MessagesManager. As that listener never gets cleaned up the MessageManager stays and with him AdmincentralUI etc... |