1988
DOI: 10.1002/spe.4380180902
|View full text |Cite
|
Sign up to set email alerts
|

Garbage collection in an uncooperative environment

Abstract: We describe a technique for storage allocation and garbage collection in the absence of significant co‐operation from the code using the allocator. This limits garbage collection overhead to the time actually required for garbage collection. In particular, application programs that rarely or never make use of the collector no longer encounter a substantial performance penalty. This approach greatly simplifies the implementation of languages supporting garbage collection. It further allows conventional compiler… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

2
238
0
3

Year Published

1996
1996
2015
2015

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 461 publications
(243 citation statements)
references
References 17 publications
2
238
0
3
Order By: Relevance
“…The most widelyused dynamic approach to handling memory leaks is garbage collection [35,36,37,38], which adds runtime overhead to the program. There is also research on dynamic memoryleak detection [39,40,41,42,43,44,45], which provides the location of an allocation which will be leaked later.…”
Section: Related Workmentioning
confidence: 99%
“…The most widelyused dynamic approach to handling memory leaks is garbage collection [35,36,37,38], which adds runtime overhead to the program. There is also research on dynamic memoryleak detection [39,40,41,42,43,44,45], which provides the location of an allocation which will be leaked later.…”
Section: Related Workmentioning
confidence: 99%
“…Boehm presents a practical implementation of a conservative garbage collector for C using conservative root scanning [9] and describes methods that reduce the likelihood for pointer misidentification during conservative root scanning [10]. Heap addresses that are found to be referenced by misidentified pointers are blacklisted, the referenced memory is not used for allocation such that future references to these addresses found during conservative root scanning will not cause the retention of memory.…”
Section: Related Workmentioning
confidence: 99%
“…In order to be precise in the absence of hardware support, object scanning requires assistance from the language runtime. Otherwise, tracing must conservatively assume all fields are references [6,7,14]. This paper quantitatively explores the design tradeoffs for object scanning in precise garbage collectors.…”
Section: Introductionmentioning
confidence: 99%