392 results about "Memory leak" patented technology

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.

The invention provides a memory control method for embedded systems. The method includes: applying for memory in an operating system, and using part of the memory as a memory pool and the other part as a reserved memory area; establishing a cache for each thread by pool management of the memory pool and thread caching technology; subjecting the reserved memory area to management by TLSF (two-level segregated fit) algorithm; dividing the memory pool into memory blocks different in size, connecting the memory blocks in the same size to form a double linked list, adding a memory management unit for each memory block, and placing the memory management unit and the memory blocks in different memory areas respectively; and establishing a memory statistical linked list for each thread to connect the memory blocks applied by the thread so as to facilitate troubleshooting of memory leak. In addition, a memory coverage checking mechanism is added without increasing cost of the memory control method.

A computer implemented method, computer program product, and data processing system for predicting a future status of a memory leak. A first set of data including memory consumption data is received at a software bundle. The software bundle is operating in an open services gateway initiative environment. Responsive to a determination that a memory leak exists, the first set of data is analyzed to predict a future status of the memory leak. The future status is stored, as stored data, in a storage device.

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.

An analysis tool for specifically identifying the cause and location of object 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, thereby providing the analysis tool operator sufficient information to make a final determination of objects that are possible candidates for memory leaks. Once the cause and location of the object memory leaks are ascertained, the analysis tool operator may analyze the memory leaks, and subsequently modify the software to reduce or eliminate the memory leaks.

A method of memory management can include creating an initial root set of pointers for a program during execution of the program and performing a marking process by iteratively marking referred objects of each pointer of the root set and expanding the root set with filtered, encoded pointers. The method also can include identifying each non-live object for any marked object as red-marked and performing, using a processor, a re-marking process on the root set in which red-marked objects are excluded. Each object of the root set not marked can be designated as including a memory leak.

A method and an apparatus for diagnosing memory leak. The method includes: tracing the allocation of objects; recording allocation paths and allocation time of each object; giving to each object one unique identifier (ID) corresponding to an allocation path; determining the allocation path to which each object belongs; organizing the objects which are allocated but still not collected, and counting the age generations of the objects of the similar type according to the allocation time of each object; ranking the allocation paths according to the age generations of the surviving objects; and analyzing the ranking of the allocation paths, in which the allocation path with higher rank is more probable to introduce memory leaks. Thus, the suspicious allocation path possibly incurring memory leaks is selected and reported to the user for analysis.

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.

Dangling pointers and memory leak locations within software are detected. As the software allocates and deallocates memory, lists of pointers referencing the memory, and pointer status, are maintained. As the software writes new addresses within pointers and reads addresses referenced by the pointers, the pointer lists are maintained to determine whether the pointers are dangling and to detect memory leak locations. A balanced binary tree having a number of nodes can be maintained. The nodes represent heap or stack records. Each heap record corresponds to heap memory that has been allocated and has a list of pointers referencing the heap memory. Each stack record corresponds to a stack within which a stack frame is allocated each time a function is entered. The stack record has frame records corresponding to the stack frames. Each frame record has a list of pointers referencing the corresponding stack frame.

The invention discloses a kind of examining method for software memory leakage. The method confirms the memory block which is applied by the application at first and the occupied time of different memory blocks, when the application runs, it records the applying and releasing information of the memory, and finds the memory block which is not released and exceeds the time, it ascertains the memory leakage point of the application; the examination to the memory leakage of application with the method has little impact on the application, it's easy to be realized and low cost, it applies to the long-term examination for the memory leakage, and helps to find the leakage fault emerged in actual application environment.

An invention is disclosed for analyzing memory leaks occurring in Java Virtual Machine (JVM) data storage, consisting of a dynamically modifiable JVM “profiler” and an “object tracker” tool for analyzing the output from the profiler. Specifically, a method and system is disclosed for programming a JVM profiler used to analyze and correct memory leaks in stored data heaps, consisting of a program segment (or “stub”) initialized by the JVM application program interface to determine the parameters to be passed to the main profiler memory leak analysis program logic, which is then initialized by the stub to examine a minimal number of “heap dumps” in order to identify data elements or objects for the existence and/or correction of memory leaks. Updated information on data elements or objects can be requested from the profiler as needed by use of the object movement tracking option to record the details of subsequent changes in data memory storage status once a heap dump has been obtained.

One embodiment relates to a method for identifying sources of memory retention in an executing application. A size of a set of objects is tracked over multiple periods. A period is determined to be a growth period if the size for the set of objects increases above a previous maximum size, and the number of growth periods is counted. The set of objects is flagged as having potential undesired object retention (a memory leak) if the number of growth periods is greater than a threshold number. Other embodiments are also disclosed.

A method for predicting memory leak in a computer program. The method includes acquiring a reference to a tested unit included in the computer program for preventing static data objects from being deallocated; repeatedly executing the tested unit for more than once; tracking which objects in the tested unit are allocated in a corresponding executing time; performing garbage collection; tracking which objects are deallocated during the garbage collection; comparing the object allocations to the object deallocations; and determining if every execution of the tested unit allocates memory that cannot be deallocated.

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.

A method to assist a software developer in optimizing performance of a Java virtual machine (Jvm) is disclosed. The method includes creating a model to predict future usage of heap memory by the Jvm. In response to the time series analysis model having an upward trend of heap memory usage, advising the developer to review a heap dump to determine if a possible memory leak exists. In response to the time series analysis model having a horizontal asymptote at a predicted future time, advising the developer to specify the maximum limit of heap memory as a function of the horizontal asymptote. In response to a heap exhaustion error, which indicates a requested usage of heap memory by the Jvm greater than a maximum limit of heap memory, determining a likely cause of the heap exhaustion error, and advising the developer to take appropriate actions to optimize the Jvm performance.

Methods of detecting a memory leak may include identifying a largest ChildNode of a ParentNode; and comparing a total size of the ParentNode to a total size of the largest ChildNode of the ParentNode. If the total size of the ParentNode is significantly larger than the total size of the largest ChildNode of the ParentNode, a possible memory leak area may be identified. Related systems and computer program products are also discussed.

The invention discloses a method of shifting memory leaking secret protection and system to realize the method, which is characterized by the following: utilizing virtual disk technique; adopting disk grade bridging method; proceeding encryption for the data in the common memory through the virtual disk with special pattern; storing the data on the shifting memory with cryptogram style; loading the virtual disk before reading or writing data; proceeding order checkout and user identification proved; non-loading without right order or special form; assuring the safety of the data in the shifting memory; setting the system as three module of server, warranting center and custom terminal. This invention can be used to various memories such as flash memory, shifting hard disk, soft disk and so on.

In one embodiment, an integrated circuit includes a logic circuit and a memory circuit that includes multiple bit lines and bit line precharge circuits. The memory circuit may include level shifters for control signals generated from logic circuit inputs, and particularly there may be one or more level shifters that generate precharge enable signals to control the bit line precharge circuits. The level shifters for the bit line precharge circuits may also be controlled, during periods of time that the memory circuit is idle, by an input control signal (FloatBL herein). If the FloatBL signal is asserted, the bit line precharge circuits may be disabled to float the bit lines. In some embodiments, the FloatBL signal may also disable bit line bit line hold circuits on the bit lines. In some embodiments, when the memory circuit is exiting an idle state, the bit line precharge circuits may be enabled in a staggered fashion.

The invention discloses a method and a device for monitoring memory, which are used for monitoring memory usage of an entity using the memory. Memory usage data of the entity to be monitored is saved in a memory cell of memory usage data; and the memory usage data of the entity to be monitored changes along with the memory usage of the entity to be monitored. The method comprises the following steps: acquiring the memory usage data of the entity to be monitored for a plurality of times from the memory cell of the memory usage data and comparing the memory usage data acquired from two consecutive times in a monitoring cycle; and if the total memory usage of the entity of the latter time is always larger than that of the former time in each acquired comparison result, confirming the phenomenon of memory leak in the entity. The method and the device provided by the invention can timely discover the problem of imperceptible memory leak in a system.

The invention provides a method for judging memory leak, comprising the following steps of: when a function application memory is judged aiming at each function in a program, accumulating the memory capacity and the application times of the named function application; when a function release memory is judged, reducing the released memory capacity from the memory capacity of the named function accumulated application and reducing release memory times from accumulated application times; sequencing the memory capacity and the times of the function application in different names in a descending mode by using the memory capacity as priority; ensuring and outputting a level of a memory leak degree according to the memory capacity and the times of the function accumulated application in different names; in addition, the invention provides a system for realizing the method in order to sequence memory distribution and information release according to the memory application times and liberate a programmer from large fussy analytical work.