Ticket #158 (new defect)
Opened 1 year ago
Photovault fills heap regardless of size
| Reported by: | harri | Owned by: | harri |
|---|---|---|---|
| Priority: | blocker | Milestone: | 0.5.future |
| Component: | common | Version: | 0.5.0-dev |
| Keywords: | Cc: | ||
| Test Case Result: |
Description
Photovault does not work too well with Java garbage collector. Regardless of the heap size it will eventually fill the heap with objects that could be garbage collected. No actual kemory leak is observed, the garbage collector just does not free memory aggressively enough.
Currently this is solved by setting maximum heap size to reasonable value (256 MB). However, this is not very good solution:
- If user opens many windows it is quite easy to get an out of memory error even if the conmputer would have plenty of RAM available.
- If maximum heap size is increased this will lead into excessive memory use. Since eventually the maximum heap size will be used, e.g. switching to other applications will cause unnecessary paging.
Note: See
TracTickets for help on using
tickets.
