Memory management configuration

• US 7,441,094 B2
• Filed: 07/05/2005
• Issued: 10/21/2008
• Est. Priority Date: 07/05/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Stephens, Maoni Z.
• Primary Examiner(s): Ellis; Kevin
• Assistant Examiner(s): Bertram; Ryan
• Application Number:
  US11/174,873
• Publication Number:
  US 20070011658A1
• Time in Patent Office: 1,204 Days
• Field of Search: 711/170
• US Class Current: 711/170
• CPC Class Codes: G06F 12/0269 Incremental or concurrent garbage collection, e.g. in real-time systems G06F12/0261 takes precedence

Abstract

Memory management within a runtime execution environment may be configured in accordance with data associated with executable code loaded therein.

Claims

1. A computer-readable medium having one or more executable instructions that, when read, cause one or more processors to:

read header data corresponding to a managed image;

determine whether the managed image is associated with a GUI-based application; and

de-allocate objects corresponding to the managed image in accordance with a functionality implemented based on whether the managed image is determined to be associated with a GUI-based application.

2. A computer-readable medium according to claim 1, wherein, when the one or more instructions cause the one or more processors to determine that the managed image is associated with a GUI-based application, the one or more instructions that cause the one or more processors to de-allocate objects further cause the one or more processors to allow allocation of other objects to occur in parallel.

3. A computer-readable medium according to claim 1, wherein, when the one or more instructions cause the one or more processors to determine that the managed image is not associated with a GUI-based application, the one or more instructions that cause the one or more processors to de-allocate objects further cause the one or more processors to suspend allocation of other objects.

4. A computer-readable medium according to claim 1, wherein, when the one or more instructions cause the one or more processors to determine that the managed image is not associated with a GUI-based application, the one or more instructions that cause the one or more processors to de-allocate objects further cause the one or more processors to suspend one or more managed threads.

5. A computer-readable medium according to claim 1, wherein, when the one or more instructions cause the one or more processors to determine that the managed image is associated with a GUI-based application, the one or more instructions that cause the one or more processors to de-allocate objects further cause the one or more processors to implement concurrent garbage collector functionality.

6. A computer-readable medium according to claim 1, wherein, when the one or more instructions cause the one or more processors to determine that the managed image is not associated with a GUI-based application, the one or more instructions that cause the one or more processors to de-allocate objects further cause the one or more processors to implement non-concurrent garbage collector functionality.

7. A computer-readable medium according to claim 1, wherein the one or more instructions that cause the one or more processors to de-allocate objects further cause the one or more processors to enable concurrent garbage collector functionality in parallel with execution of a managed thread.

8. A computer-readable medium according to claim 1, wherein the one or more instructions that cause the one or more processors to de-allocate objects further cause the one or more processors to suspend a managed thread during garbage collection during non-concurrent garbage collector functionality.

9. A computer-implemented method, comprising:

reading header data corresponding to a managed image;

determining whether the managed image is associated with a GUI-based application; and

de-allocating objects corresponding to the managed image in accordance with a functionality implemented based on whether the managed image is determined to be associated with a GUI-based application.

10. A method according to claim 9, wherein de-allocating objects comprises allowing allocation of other objects to occur in parallel if it is determined that the managed image is associated with a GUI-based application.

11. A method according to claim 9, wherein de-allocating objects comprises suspending allocation of other objects if it is determined that the managed image is not associated with a GUI-based application.

12. A method according to claim 9, wherein de-allocating objects comprises suspending managed threads if it is determined that the managed image is not associated with a GUI-based application.

13. A method according to claim 9, wherein de-allocating objects comprises allowing managed threads if it is determined that the managed image is associated with a GUI-based application.

14. A method according to claim 9, further comprising enabling concurrent garbage collector functionality in parallel with execution of a managed thread.