<--- Back to Details
First PageDocument Content
Automatic memory management / Graph theory / Data types / Unreachable memory / Object-oriented programming / Garbage collection / Memory leak / Finalizer / Reference counting / Computing / Software engineering / Memory management
Date: 2003-07-09 11:41:16
Automatic memory management
Graph theory
Data types
Unreachable memory
Object-oriented programming
Garbage collection
Memory leak
Finalizer
Reference counting
Computing
Software engineering
Memory management

Does Java™ Technology Have Memory Leaks? Ed Lycklama Chief Technology Officer, KL Group Inc[removed], Ed Lycklama

Add to Reading List

Source URL: www.cs.kent.ac.uk

Download Document from Source Website

File Size: 1.017,04 KB

Share Document on Facebook

Similar Documents

Software engineering / Computing / Memory management / Computer programming / Finalizer / Finalization / Garbage collection / Manual memory management / Resource management / Resource Acquisition Is Initialization / Reference counting / Garbage

Adding Reference Counting to the Shared Source Common Language Infrastructure _Chris_Sells_ and _Christopher_Tavares_, Abstract Moving to a garbage-collected environment in the Common Language Runtime has, for th

DocID: 1pU1s - View Document

Destructors, Finalizers, and Synchronization Hans-J. Boehm HP Laboratories

Destructors, Finalizers, and Synchronization Hans-J. Boehm HP Laboratories

DocID: 1m2f7 - View Document

Software-Architecture Recovery from Machine Code∗ Venkatesh Karthik Srinivasan Thomas Reps  University of Wisconsin

Software-Architecture Recovery from Machine Code∗ Venkatesh Karthik Srinivasan Thomas Reps University of Wisconsin

DocID: 1lH2O - View Document

Finalizers, Threads, and the Java Memory Model Hans-J. Boehm HP Labs © 2004 Hewlett-Packard Development Company, L.P.

Finalizers, Threads, and the Java Memory Model Hans-J. Boehm HP Labs © 2004 Hewlett-Packard Development Company, L.P.

DocID: 1kH0Y - View Document

PDF Document

DocID: 1jbFr - View Document