395 results about "Memory leak" patented technology

A system and method for detecting memory leaks includes a monitoring agent, a user interface for configuring operating parameters and a reporting mechanism. The monitoring agent determines allocated memory levels of a monitored application at a sampling frequency and determines when a then-existing “peak” memory level has increased. The monitored application is determined to be leaking memory when a determined number of increases in the peak allocated memory level are detected. The determined number may be fixed ahead of time or may be calculated dynamically based on user specified parameters. When a given memory leakage rate is exceeded, an alarm response is taken, which may be either a specified notification of the alarm or an action. Certain increases in the peak allocated memory levels are ignored as not necessarily being indicative of a memory leak condition, such as during startup of the program or between rapidly, closely-occurring increases in the peak allocated memory level.

A low overhead method for identifying memory leaks is provided. The low overhead method includes a) detecting completion of a garbage collection cycle; and b) identifying a boundary between used objects in memory and free memory space. The steps of a) and b) are repeated and then it is determined if there is an existing memory leak based upon evaluation of boundary identifiers. A computer readable media and a system for identifying memory leaks for an object-oriented application are also provided.

An automation infrastructure which automatically analyzes software faults and / or bugs related to a product defect is provided. More particularly, the system can automatically analyze and detect symptoms in the forms of crash dump, memory leak, corruption and test issues etc. In accordance therewith, aspects can automatically search for and locate existing defect reports, if such existing reports are available. Moreover, aspects can automatically report new defects in a defect tracking database or other tracking mechanism.

Potential sources of memory leaks are identified by tracking the size of groups of stored items and determining based on the growth pattern of the groups whether the groups of stored items are potential sources of memory leaks. An example of a group of stored items is an instance of a Java collection. If the growth pattern of a particular group of stored items indicates that it may be the source of a memory leak, that group is reported to a user and will continue to be tracked.

Methods, systems, and media to enhance memory leakage management by identifying a suspect allocation pattern during execution of a task, which may be indicative of memory leakage and implementing measures to protect against memory leakage based upon the suspect allocation pattern, are disclosed. More specifically, embodiments may detect a suspect allocation pattern by monitoring memory allocations and deallocations for tasks. The pattern of memory allocations and deallocations may then be analyzed to determine whether a suspect allocation pattern exists. For instance, the memory allocations and deallocations may be compared to determine whether there is an increasing net residual allocation left by the task after it has reached a quiescent runtime state. In some embodiments, a suspect allocation pattern exists if the total memory allocation for a task continues to rise after a pre-determined time period.

Embodiments of the invention relate to identifying sources of memory leaks. In an embodiment, an agent collects information related to object allocations and de-allocations in accordance with a sampling period, and, based on the relationship between object allocations and de-allocations, the agent analyzes the data and reports the results. Other embodiments are also disclosed.

The invention discloses a method and a device for monitoring leakage of a memory. The method comprises the following steps of monitoring the operation information of a user interface of a user on an application program, and storing the monitored operation information of the user interface; monitoring the usage condition of the memory of a system, and obtaining the information of the memory of the system; obtaining the key field value for indicating the usage condition of the memory in the application program from the information of the memory; if the first comparison result indicates that the key field value is greater than the first preset threshold, determining the occurrence of leakage of the memory, and utilizing the operation information of the user interface and the information of the memory to generate alarming information; after receiving triggering information, outputting the alarming information. The method and the device have the advantage that the particular operation scene which occurs during the leakage of the memory can be determined, and the corresponding LOG information is analyzed, so a developer can quickly locate the use problem of the memory in the program.

A software program (12) is configured to initiate, process, and terminate user sessions (22, 26). A resource deallocation module (50) is linked to the software program (12) to deallocate allocated external resources of each object of a user session responsive to an impending termination of said user session. An automatic memory management module (40) is invoked by the software program with respect to said user session subsequent to the deallocation performed by the resource deallocation module (50) and prior to the termination of said user session.

The invention relates to an embedded system testing method. Hardware and assistance software are adopted; firstly, pile pitching is carried out on a source code, a sentence is inserted in a specific place, then a pile pitching document is compiled and downloaded; when a target board operates to a pile pitching point, a bus presents specific signals, the auxiliary hardware of a data acquisition unit acquires the signals of the pile pitching points; subsequently, the acquisition point information is packed and sent to a testing result analyzing software for result analysis, thus the embedded system testing is realized. The testing includes coverage analysis, performance analysis, memory leak analysis, array out-of-range, variable control, trace following, Task monitoring, ISR monitoring, TaskISR switching monitoring, etc.

A system and method for detecting memory leaks includes a monitoring agent, a user interface for configuring operating parameters and a reporting mechanism. The monitoring agent determines allocated memory levels of a monitored application at a sampling frequency and determines when a then-existing “peak” memory level has increased. The monitored application is determined to be leaking memory when a determined number of increases in the peak allocated memory level are detected. The determined number may be fixed ahead of time or may be calculated dynamically based on user specified parameters. When a given memory leakage rate is exceeded, an alarm response is taken, which may be either a specified notification of the alarm or an action. Certain increases in the peak allocated memory levels are ignored as not necessarily being indicative of a memory leak condition, such as during startup of the program or between rapidly, closely-occurring increases in the peak allocated memory level.

An analysis tool for specifically identifying the cause and location of critical memory leaks within a large software system is provided. The analysis tool transparently adds multiple processing threads that collaborate to identify sources of potential memory leaks in the software being analyzed. These threads provide notifications of object classes executing in the software that have had excessive instance counts or have exceeded the average lifetime of an object. A stack walkback is performed on objects being monitored as an out-of-memory condition approaches and while there is still sufficient memory available to unwind and store the stack walkback. By saving the stack walkbacks just prior to the out-of-memory failure, the analysis tool operator is thereby provided sufficient information to make a final determination of objects that are possible candidates for memory leaks and subsequently modify the software to reduce or eliminate the memory leaks.