Memory management techniques selectively using mitigations to reduce errors

Abstract

Techniques for performing memory management to mitigate memory errors. In accordance with the principles described herein, a memory management module may be implemented that acts in different modes of operation for each of one or more software modules issuing requests for performance of memory operations to the memory management module. In one mode of operation, one or more mitigation actions may be performed by the memory management module in addition to or instead of the memory operation requested by the calling software module, such that the memory operations are performed in accordance with the mitigation actions. These mitigation actions may serve to reduce a likelihood of a memory error negatively affecting the calling software module. In another mode of operation, the memory management module performs memory operations as requested, without performing mitigation actions.

Description

BACKGROUND[0001]In multi-purpose computing devices, operating systems are typically, though not exclusively, used to manage memory of the computing device for use by one or more applications executing on the computing device. For example, if two applications access memory on the computing device, then the operating system may allocate portions of the memory for use by the two applications such that both can access memory without corrupting data stored by the other.[0002]This management and arbitration may be necessary to alleviate problems that may arise if an application attempts to use memory being used by another. For example, if two applications both attempt to use the same portion of a memory in the same or overlapping time periods, then the second may overwrite the data of the first, and the first may be unable to execute properly or even crash. Errors such as these have a significant impact on the user experience, particularly if they occur frequently.[0003]Operating systems ...

AI Technical Summary

Benefits of technology

[0008]Applicants have recognized and appreciated that applications may operate more reliable, and a user experience improved, by using memory management to compensate for programming bugs in the software applications that cause memory errors. Applicants have recognized that many memory errors may be caused by inconsistencies in memory operations performed by the applications, and that the effects of these programming bugs may be mitigated by anticipating these inconsistencies and performing memory management in a way to correct for them. For example, by allocating more resources (such as memory and / or time) to an application than the application requests, a memory management module may compensate for a bug in the application that causes the application to access more memory than it requested or using memory after it signals it is done with the memory. Further, in some instances, a memory management module may mitigate errors by not executing memory operations requested by applications, for example, if it is detected that input information for the operations is incorrect.

[0009]Many different types of errors may be mitigated with different types of mitigation actions, examples of which are discussed in greater detail below. Applicants have appreciated, however, that mitigations such as these may have a significant impact on the efficiency of the computing devices and may impact performance of applications executing on those devices. Evaluating and manipulating a memory operation each time one is requested may add time to the completion of a request, and allocating more memory than requested uses more memory and thus may reduce resources available to the system. Applicants have appreciated the desirability of a memory management module having mitigations which is able to be selectively enabled per application.

[0010]In accordance with the principles described herein, a memory management module may be implemented that has different modes of operation for each of one or more software modules issuing to the memory management module requests for performance of memory operations. In one mode of operation, one or more mitigation actions may be performed by the memory management module in addition to or instead of the memory operation requested by the calling software module, such that the memory operations are performed in accordance with the mitigation actions. These mitigation actions may serve to reduce a likelihood of a memory error affecting the calling software module. In another mode of operation, the memory management module performs memory operations as requested, without performing mitigation actions. A memory management module may maintain a record in a data store associated with the memory management module, the record having at least one entry for each calling software module indicating the mode in which the memory management module should operate for the calling software module.

[0011]Operating a memory management module in accordance with some or all of the principles described herein may reduce a the likelihood of software modules, such as user applications, executing improperly or crashing, which may serve to improve a user experience while using these software modules.

Problems solved by technology

For example, if two applications both attempt to use the same portion of a memory in the same or overlapping time periods, then the second may overwrite the data of the first, and the first may be unable to execute properly or even crash.

Errors such as these have a significant impact on the user experience, particularly if they occur frequently.

Some software applications that may execute processes interacting with an operating system, for example, may include bugs or other programming flaws related to performing memory operations, and the software applications may fail as a result of memory errors even when the memory manager executes the memory operations correctly.

These memory errors may result from inconsistencies that may arise between memory operations.

The inconsistencies between operations—in this example, the inconsistency in size between the first amount and the second amount—may cause memory errors that lead to failures in the software application.

These failures could include improper executions caused by the memory errors, or even catastrophic errors or “crashes” that halt execution of the application.

In this way, the debugging tool may identify errors and report them to the developer.

Such debugging tools, however, may not be used during runtime of a software application.

Such attempts to resolve crashes experienced during runtime have traditionally been limited to detecting when such errors occur and reporting the conditions of the crash to a central aggregation point that may then inform the developer of the available information about the error.

Further, in some instances, a memory management module may mitigate errors by not executing memory operations requested by applications, for example, if it is detected that input information for the operations is incorrect.

Evaluating and manipulating a memory operation each time one is requested may add time to the completion of a request, and allocating more memory than requested uses more memory and thus may reduce resources available to the system.

Images