| Summary: | JavaTextTools keeps last document in memory | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Darin Swanson <Darin_Swanson> | ||||
| Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | eclipse, Tod_Creasey | ||||
| Version: | 3.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Darin Swanson
Created attachment 10403 [details]
Reduced reference graph showing the Lines kept in memory
There's no API to remove the document or reset it by providing null. This can result in most of the state of the last debug session remaining in memory. The InstructionPointerAnnotation (which has a reference to a stack frame) is retained in memory via the retention of the removed annotations associated with the annotation model of the document. My mistake...ignore comment #3...sorry We'd need an additional API method to free the state. No action for 3.0. Adding my name to the cc list as we are now tracking performance issues more closely. Please remove the performance keyword if this is not a performance bug. *** Bug 92272 has been marked as a duplicate of this bug. *** This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |