Task #4183 (closed)
Make sure that static fields are being used properly
|Reported by:||mlinkert||Owned by:|
Description (last modified by mlinkert)
There are several static (non-final) HashMaps/Hashtables? throughout the reader classes that could be made final.
The 'uuids' field in OMETiffWriter is static, but it is never cleared. If possible, it would be best to make this field non-static, or at least provide a mechanism for clearing stale entries to prevent memory leaks.
Similarly, the Location has several static fields (including 'idMap' and 'fileListings') for which it would be nice to have a master reset method that clears the HashMaps/Hashtables? and resets associated fields to their original state.
Finally, we need to ensure that static fields are accessed in a thread-safe manner.
Change History (9)
comment:2 Changed 10 years ago by mlinkert
- Description modified (diff)
- Keywords sprint-1 removed
- Remaining Time set to 0.5
- Sprint set to 2011-02-10 (5)
comment:8 Changed 9 years ago by mlinkert
- Owner mlinkert-x deleted
- Status changed from accepted to new