Memory Management

Memory Management

Memory Management For most programming languages memory management has two parts: (1) Static - global data, compiled code, runtime system (2) Dynamic - runtime stack (activation record stack), heap (!) Chap. 14 Typical Memory Layout 0 Compiled code, RTS, Library code Heap Manager static A typical memory layout for languages such as C and Java Global data Stack Pointer Runtime stack NOTE: if the runtime stack and the heap meet Þ out of memory dynamic Heap FF..FF The Heap Runtime systems allocate dynamically created objects on the heap by a call to the heap manager. In Java the heap manager is called with the new keyword. In C the heap manager is called using the malloc function. Observation: In languages like Java and ML heap memory is reclaimed by the heap manager automatically via garbage collection when it is no longer used. In C the programmer has to explicitly manage heap memory with malloc/free function calls. This is error prone and leads to the (in)famous dangling pointer reference (free called too early) and the memory leak (free never called) problems. Example C (Memory Leak) Program Heap Manager struct Object * o; void f() { o: Object o = malloc(sizeof(struct Object)); o: Object struct Object * p = o; p: o: Object o = NULL; p: o: Object } p: Note: the heap manager has not way of knowing (pop activation record off the runtime stack) that this memory is no longer used Þmemory leak Example C (Dangling Pointer) Program Heap Manager void f() { struct Object * o = malloc(sizeof(struct Object)); o: Object Dangling Pointer free(o); o: Object struct Foo * p = malloc(sizeof(struct Foo)); o: Object Foo p: o->ObjectAttribute = value; Corruption of the p object! p->Print(); free(p); } Example Java (Garbage Collection) Program Heap Manager Reference Count void f() { Object o = new Object(); o: 1 Object Object p = o; o: 2 Object p: o: 1 Object p = null; p: The heap manager notices that this memory is no longer used and therefore can safely } delete it. (pop activation record off the runtime stack) o: 0 Object p: Java uses a garbage collection technique called reference counting..

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    6 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us