Proceedings of the 5th International Workshop on Java Technologies for Real-Time and Embedded Systems - JTRES '07 2007
DOI: 10.1145/1288940.1288953
|View full text |Cite
|
Sign up to set email alerts
|

Garbage collection for safety critical Java

Abstract: The Real-time Specification for Java and the upcoming, and more restricted, Safety Critical Java standard have been designed to allow programmers to avoid pauses caused by automatic memory management algorithms. Dynamic memory is user-managed using a region-based allocation scheme known as scoped memory areas. However, usage of those scoped memories is cumbersome and often leads to runtime errors. In this paper we focus on the safety critical subset of the Real-time Specification for Java and propose a real-ti… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
18
0

Year Published

2008
2008
2024
2024

Publication Types

Select...
4
2
1

Relationship

3
4

Authors

Journals

citations
Cited by 17 publications
(18 citation statements)
references
References 25 publications
0
18
0
Order By: Relevance
“…The implemented collector on JOP is an incremental collector [29,36] based on the copy collector by Cheney [13] and the incremental version by Baker [8]. To avoid the expensive read barrier in Baker's collector all object copies are performed concurrently by the collector.…”
Section: Methodsmentioning
confidence: 99%
See 1 more Smart Citation
“…The implemented collector on JOP is an incremental collector [29,36] based on the copy collector by Cheney [13] and the incremental version by Baker [8]. To avoid the expensive read barrier in Baker's collector all object copies are performed concurrently by the collector.…”
Section: Methodsmentioning
confidence: 99%
“…It is also essential to minimize the overhead introduced by readand write-barriers, which are necessary for synchronization between the GC thread and the application threads. The design of a GC within these constraints is described in [36,33] and summarized in Section 4.…”
Section: Introductionmentioning
confidence: 99%
“…Work has been done to develop garbage collectors suitable for hard-real time systems and while it can be proved that a GC task can be scheduled on hardreal time systems given that allocation rates of the mutator task are known (see e.g., [119]), safety-critical systems will need a certified GC, i.e., a GC that can be proved in a formal way to be correct. Efforts towards a certified GC [55,84,86,129] have focused on correctly specifying the collector-mutator interface in order to avoid implementers either on the collector or mutator side to violate intended invariants [83].…”
Section: Certifiable Garbage Collectormentioning
confidence: 99%
“…The key issue of time-based real-time GC is how much time should be given to the collector. Schoeberl and Vitek [54] presented the algorithm to compute the GC quota and interval in their study. Cho et al [55] used Yu Sun and Wei Zhang statistical tools to guarantee the algorithm's effectiveness and superiority.…”
Section: B Time-predictable Garbage Collectionmentioning
confidence: 99%