Fourth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing. ISORC 2001
DOI: 10.1109/isorc.2001.922863
|View full text |Cite
|
Sign up to set email alerts
|

Region-based memory management for real-time Java

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 16 publications
(9 citation statements)
references
References 7 publications
0
9
0
Order By: Relevance
“…Beebe and Rinard use this approach [11], and their implementation uses ve runtime heap checks to ensure that a critical real-time thread does not manipulate heap references. Alternatively, the solution proposed in [6] instruments the bytecode interpreter, avoiding space problems, but this still requires a complementary solution to handle native code.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Beebe and Rinard use this approach [11], and their implementation uses ve runtime heap checks to ensure that a critical real-time thread does not manipulate heap references. Alternatively, the solution proposed in [6] instruments the bytecode interpreter, avoiding space problems, but this still requires a complementary solution to handle native code.…”
Section: Related Workmentioning
confidence: 99%
“…The IllegalAssignment() exception throws when detecting an attempt to make an illegal pointer. Since assignment rules cannot be fully enforced by the compiler, some dangling pointers must be detected at runtime, which requires the introduction of write barriers [6]. That is, to introduce a code checking for dangling pointers when creating an assignment.…”
Section: The Rtsj Memory Modelmentioning
confidence: 99%
“…However, static and dynamic techniques can be combined to provide more robustness and predictability of RTSJ applications. The idea of using both write barrier and a stack of scoped areas ordered by life-times to detect illegal inter-area assignments was first introduced in [4]. The most common approach to implement read/write barriers is by inline code, consisting in generating the instructions executing barrier events for every load/store operation.…”
Section: Related Workmentioning
confidence: 99%
“…In order to avoid the garbage collector's affection on the execution time and ensure real-time performance, RTSJ provides a more complex memory management system which is different from general Java [10][11]. Four different types of memory are defined in RTSJ, and they are HeapMemory, ScopedMemory, ImmortalMemory and ImmortalPhysicalMemory.…”
Section: Introductionmentioning
confidence: 99%