Dynamic code generation and memory management for component object model data constructs

• US 10,248,415 B2
• Filed: 04/20/2016
• Issued: 04/02/2019
• Est. Priority Date: 05/19/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Lucco, Steven, Lafreniere, Louis, Qu, Yong
• Primary Examiner(s): Nguyen, Duy Khuong T
• Application Number:
  US15/133,998
• Publication Number:
  US 20160232002A1
• Time in Patent Office: 1,077 Days
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/75 Structural analysis for program understanding
• CPC Class Codes: G06F 9/449 Object-oriented method invocation or resolution
• CPC Class Codes: G06F 9/5022 Mechanisms to release resources

Abstract

Dynamic code generation and memory management techniques are provided for component object model (COM) objects with corresponding representations in script code and native code. A browser component can receive script code including the code representing the COM object and a marshaling component is provided that marshals, based on a request for native code representing the COM object, the code representing the COM object to the native code based on a pre-constructed intermediate data structure. The pre-constructed intermediate data structure, such as a virtual table, is pre-constructed based on a dynamic type representation associated with a prototype of the COM object and cached for re-use by the marshaling component. Other embodiments provide finalizer support for memory management of COM objects having script and native world representations including an implementation of a two-phase commit protocol that enables efficient and conservative recycling of objects and associated memory.

Claims

1. A computing device, comprising:

a processor communicatively coupled to a memory, the memory storing computing executable instructions that when executed cause the processor to;

initiate a request to reclaim memory associated with a script code object with a dependency to a native code object represented in native code;

in a first phase, request the script code object and the native code object to prepare for the request to reclaim the memory associated with the script code object; and

in a second phase, only in response to receiving confirmation from the script code object that the script code object is prepared for the request and in response to receiving confirmation from the native object that the native object is prepared for the request, unwind the dependency to the native code object represented in native code and proceed to reclaim the memory associated with the script code object.

2. The computing device of claim 1, wherein the request, the unwind and the proceed adhere to a two-phase commit protocol with the request corresponding to a prepare phase, and the unwind and proceed corresponding to a commit phase.

3. The computing device of claim 1, wherein the initiate the request includes initiating a request to reclaim memory associated with the script code object having a pointer to the native code object.

4. The computing device of claim 1, wherein the unwind the dependency includes releasing the native code object.

5. The computing device of claim 1, wherein the unwind the dependency includes decrementing a reference count associated with the native code object.

6. The computing device of claim 1, wherein the first component is further configured to check references of the native code object.

7. The computing device of claim 1, wherein the first component is further configured to check references of the native code object including determining an additional dependency of the native code object that prevents the confirmation from the native code object.

8. A method, comprising:

initiating a request to reclaim memory associated with a script code object with a dependency to a native code object represented in native code;

in a first phase, requesting the script code object and the native code object to prepare for the request to reclaim the memory associated with the script code object; and

in a second phase, only in response to receiving confirmation from the script code object that the script code object is prepared for the request and in response to receiving confirmation from the native object that the native object is prepared for the request, unwinding the dependency to the native code object represented in native code and proceeding to reclaim the memory associated with the script code object.

9. The method of claim 8, wherein the requesting, the unwinding and the proceeding adhere to a two-phase commit protocol with the requesting corresponding to a prepare phase, and the unwinding and proceeding corresponding to a commit phase.

10. The method of claim 8, wherein the initiating the request includes initiating a request to reclaim memory associated with the script code object having a pointer to the native code object.

11. The method of claim 8, wherein the unwinding the dependency includes releasing the native code object.

12. The method of claim 8, wherein the unwinding the dependency includes decrementing a reference count associated with the native code object.

13. The method of claim 8, further comprising:

checking references of the native code object.

14. The method of claim 8, further comprising:

checking references of the native code object including determining an additional dependency of the native code object that prevents the confirmation from the native code object.

15. A computer-readable storage medium comprising computer-readable instructions that, in response to execution by a computing system, cause the computing device including at least one processor to perform operations, comprising:

initiating a request to reclaim memory associated with a script code object with a dependency to a native code object represented in native code;

in a first phase, requesting the script code object and the native code object to prepare for the request to reclaim the memory associated with the script code object; and

in a second phase, only in response to receiving confirmation from the script code object that the script code object is prepared for the request and in response to receiving confirmation from the native object that the native object is prepared for the request, unwinding the dependency to the native code object represented in native code and proceeding to reclaim the memory associated with the script code object.

16. The computer-readable storage medium of claim 15, wherein the requesting, the unwinding and the proceeding adhere to a two-phase commit protocol with the requesting corresponding to a prepare phase, and the unwinding and proceeding corresponding to a commit phase.

17. The computer-readable storage medium of claim 15, wherein the initiating the request includes initiating a request to reclaim memory associated with the script code object having a pointer to the native code object.

18. The computer-readable storage medium of claim 15, wherein the unwinding the dependency includes releasing the native code object.

19. The computer-readable storage medium of claim 15, wherein the unwinding the dependency includes decrementing a reference count associated with the native code object.

20. The computer-readable storage medium of claim 15, further comprising:

checking references of the native code object including determining an additional dependency of the native code object that prevents the confirmation from the native code object.