Improvements of Recovery from Marking Stack Overflow in Mark Sweep Garbage Collection

DOI IPSJ Web Site Web Site 3 References
  • Ugawa Tomoharu
    Graduate School of Informatics and Engineering, The University of Electro-Communications
  • Iwasaki Hideya
    Graduate School of Informatics and Engineering, The University of Electro-Communications
  • Yuasa Taiichi
    Graduate School of Informatics, Kyoto University

Search this article

Description

Mark sweep garbage collection (GC) is usually implemented using a mark stack for a depth first search that marks all objects reachable from the root set. However, the required size of the mark stack depends on the application, and its upper bound is proportional to the size of the heap. It is not acceptable in most systems to reserve memory for such a large mark stack. To avoid unacceptable memory overhead, some systems limit the size of the mark stack. If the mark stack overflows, the system scans the entire heap to find objects that could not be pushed due to overflow and traverses their children. Since the scanning takes a long time, this technique is inefficient for applications that are likely to cause overflows. In this research, we propose a technique to record rough locations of objects that failed to be pushed so that they can be found without scanning the entire heap. We use a technique similar to the card table of mostly concurrent GC to record rough locations.

Journal

References(3)*help

See more

Keywords

Details 詳細情報について

Report a problem

Back to top