Abstract: Some computing devices have limited resources such as, for example, battery power. When a user ceases to interact with an application, execution of the application can be moved to background and the application can be paused. During the time period in which the application is paused, the application consumes no CPU cycles because executing managed threads of the paused application are stopped, and native threads are prevented from running using asynchronous procedure calls.

Abstract: Architecture that computes smart-hashes (checksums) in a central server, and in a language agnostic way. The process comprises: decompiling the binaries using language/platform specific tool(s); applying configurable filtering of the decompiled output and only keeping contents that are semantically relevant; generating a hash (checksum) on those filtered semantically relevant content; and, downloading to each of the machines in the data-center a checksum list from a repository. When an assembly is requested to be loaded on a server, a check is made if another assembly with the same checksum has already been loaded on the server: if yes, the assemblies are semantically same, and hence, the download is not completed, and the assembly already present on the server is used.

Abstract: Some computing devices have limited resources such as, for example, battery power. When a user ceases to interact with an application, execution of the application can be moved to background and the application can be paused. During the time period in which the application is paused, the application consumes no CPU cycles because executing managed threads of the paused application are stopped, and native threads are prevented from running using asynchronous procedure calls.

Abstract: A method includes selectively controlling, at a computing device having a memory, initiation of a full garbage collection operation based on a total resource usage metric and a managed object metric. The managed object metric is based on objects managed by a runtime application.

Abstract: Some computing devices have limited resources such as, for example, battery power. When a user ceases to interact with an application, execution of the application can be moved to background and the application can be paused. During the time period in which the application is paused, the application consumes no CPU cycles because executing managed threads of the paused application are stopped, and native threads are prevented from running using asynchronous procedure calls.

Abstract: A method includes selectively controlling, at a computing device having a memory, initiation of a full garbage collection operation based on a total resource usage metric and a managed object metric. The managed object metric is based on objects managed by a runtime application.

Abstract: Architecture that computes smart-hashes (checksums) in a central server, and in a language agnostic way. The process comprises: decompiling the binaries using language/platform specific tool(s); applying configurable filtering of the decompiled output and only keeping contents that are semantically relevant; generating a hash (checksum) on those filtered semantically relevant content; and, downloading to each of the machines in the data-center a checksum list from a repository. When an assembly is requested to be loaded on a server, a check is made if another assembly with the same checksum has already been loaded on the server: if yes, the assemblies are semantically same, and hence, the download is not completed, and the assembly already present on the server is used.

Abstract: Some computing devices have limited resources such as, for example, battery power. When a user ceases to interact with an application, execution of the application can be moved to background and the application can be paused. During the time period in which the application is paused, the application consumes no CPU cycles because executing managed threads of the paused application are stopped, and native threads are prevented from running using asynchronous procedure calls.

Abstract: A method includes selectively controlling, at a computing device having a memory, initiation of a full garbage collection operation based on a total resource usage metric and a managed object metric. The managed object metric is based on objects managed by a runtime application.

Abstract: Some computing devices have limited resources such as, for example, battery power. When a user ceases to interact with an application, execution of the application can be moved to background and the application can be paused. During the time period in which the application is paused, the application consumes no CPU cycles because executing managed threads of the paused application are stopped, and native threads are prevented from running using asynchronous procedure calls.

Abstract: A generational garbage collector utilizes a pool-based heap to store objects dynamically generated at runtime. The pool-based heap is configured as a collection of pools where each pool stores objects associated with the same generation. Each pool contains a pool header that identifies the generation of all objects within the pool. The pools are aligned to a memory boundary that is a multiple of the pool size. Select bits of an object's memory address may be used to access the pool header so that an object's generation, which is needed in various phases of the garbage collection process, is readily determined.

Abstract: Some computing devices have limited resources such as, for example, battery power. When a user ceases to interact with an application, execution of the application can be moved to background and the application can be paused. During the time period in which the application is paused, the application consumes no CPU cycles because executing managed threads of the paused application are stopped, and native threads are prevented from running using asynchronous procedure calls.

Abstract: A generational garbage collector utilizes a pool-based heap to store objects dynamically generated at runtime. The pool-based heap is configured as a collection of pools where each pool stores objects associated with the same generation. Each pool contains a pool header that identifies the generation of all objects within the pool. The pools are aligned to a memory boundary that is a multiple of the pool size. Select bits of an object's memory address may be used to access the pool header so that an object's generation, which is needed in various phases of the garbage collection process, is readily determined.

Abstract: A method includes selectively controlling, at a computing device having a memory, initiation of a full garbage collection operation based on a total resource usage metric and a managed object metric. The managed object metric is based on objects managed by a runtime application.

Abstract: Verifying the compliance of user interfaces with desired guidelines. In an embodiment, the desired guidelines are specified as a set of validation rules that are to be checked against image frames having multiple display portions. Each validation rule is specified as being applicable to specific interface characteristics. Thus, each validation rule is checked against display portions having matching interface characteristics.