Try OpenEdge Now
skip to main content
Developing AppServer Applications
Design and Implementation Considerations : Secondary performance considerations : Garbage collection for class-based objects
 

Garbage collection for class-based objects

Garbage collection protects against memory leaks by automatically deleting class-based objects that are no longer referenced. For AppServer applications, garbage collection will run always before a switch in the connection context. Thus, AppServer applications running in all modes are protected by garbage collection. For more information on class-based objects, see OpenEdge Development: Object-oriented Programming.