ACM Home Page
Please provide us with feedback. Feedback
The CLOSER: automating resource management in java
Full text PdfPdf (329 KB)
Source
International Symposium on Memory Management archive
Proceedings of the 7th international symposium on Memory management table of contents
Tucson, AZ, USA
SESSION: Garbage collection & resource management table of contents
Pages 1-10  
Year of Publication: 2008
ISBN:978-1-60558-134-7
Authors
Isil Dillig  Stanford University, Stanford, CA, USA
Thomas Dillig  Stanford University, Stanford, CA, USA
Eran Yahav  IBM T.J. Watson Research Center, Hawthorne, USA
Satish Chandra  IBM T.J. Watson Research Center, Hawthorne, USA
Sponsors
ACM: Association for Computing Machinery
SIGPLAN: ACM Special Interest Group on Programming Languages
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 5,   Downloads (12 Months): 59,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1375634.1375636
What is a DOI?

ABSTRACT

While automatic garbage collection has relieved programmers from manual memory management in Java-like languages, managing resources remains a considerable burden and a source of performance problems. In this paper, we present a novel technique for automatic resource management based on static approximation of resource lifetimes. Our source-to-source transformation tool, CLOSER, automatically transforms program code to guarantee that resources are properly disposed and handles arbitrary resource usage patterns. CLOSER generates code for directly disposing any resource whose lifetime can be statically determined; when this is not possible, CLOSER inserts conditional disposal code based on interest-reference counts that identify when the resource can be safely disposed. The programmer is only required to identify which types should be treated as resources, and what method to invoke to dispose each such resource. We successfully applied CLOSER on a moderate-sized graphics application that requires complex reasoning for resource management.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
Bug reports for Eclipse projects. See bugs.eclipse.org/bugs.
 
3
Eclipse Java Development Tools. See www.eclipse.org.
 
4
The using statement. See C# Language Specification, msdn.microsoft.com.
 
5
Watson Libraries for Program Analysis (WALA). Available at wala.sf.net.
6
7
8
9
10
11
12
13
14
15
16
17
18
19
 
20
Livshits, V. B. Turning Eclipse against itself: Finding bugs in Eclipse code using lightweight static analysis. Eclipsecon '05 Research Exchange, Mar. 2005.
21
 
22
Shaham, R., Yahav, E., Kolodner, E. K., and Sagiv, S. Establishing local temporal heap safety properties with applications to compile-time memory management. In SAS (2003), R. Cousot, Ed., vol. 2694 of Lecture Notes in Computer Science, Springer, pp. 483--503.
23
24


Collaborative Colleagues:
Isil Dillig: colleagues
Thomas Dillig: colleagues
Eran Yahav: colleagues
Satish Chandra: colleagues