Determining origins of memory leaks in source code
A computer-implemented method, a computer program product, and a computer system for determining origins of memory leaks in source code. A computer system writes a first memory dump, in response to a memory leak being detected. A computer system searches the first memory dump to determine types of suspect leaking collections. A computer system creates identifiers for respective instances of each of the types. A computer system writes a second memory dump, in response to a continued memory leak being detected. A computer system determines which unique identifiers from the second memory dump correspond to growing collection objects of the types. A computer system tracks code paths of calls that add objects to collections whose identifiers match one of the unique identifiers. A computer system logs the code paths for review by developers.
1. A computer-implemented method for determining origins of memory leaks in source code, the method comprising: in response to a memory leak being detected, writing a first memory dump; searching the first memory dump to determine types of suspect leaking collections; creating unique identifiers for respective instances of each of the types; in response to a continued memory leak being detected, writing a second memory dump; determining which unique identifiers from the second memory dump correspond to growing collection objects of the types; adding code to methods of the types of the suspect leaking collections to make the methods uniquely label the respective instances when a next time the methods are called for the respective instances; tracking code paths of calls that add objects to collections whose identifiers match one of the unique identifiers; and logging the code paths for review by developers.
2. The computer-implemented method of claim 1 , further comprising:
monitoring for signs of the memory leak; and
monitoring for signs of the continued memory leak.
3. The computer-implemented method of claim 1 , further comprising:
adding code to methods of suspect leaking collection types that add objects to a collection instance; and
wherein the code determines whether the collection instance being called matches an identifier of a suspect leaking collection instance.
4. The computer-implemented method of claim 1 , wherein an automated process of determining the origins of the memory leaks requests a target process monitored for the memory leaks to write the first memory dump, wherein the target process writes the first memory dump on storage storing memory dumps and stack traces.
5. The computer-implemented method of claim 1 , wherein an automated process of determining the origins of the memory leaks requests a target process monitored for the memory leaks to write the second memory dump, wherein the target process writes the second memory dump on storage storing memory dumps and stack traces.
6. The computer-implemented method of claim 1 , wherein an automated process of determining the origins of the memory leaks requests a target process monitored for the memory leaks to log the code paths, wherein the target process logs the code paths on storage storing memory dumps and stack traces.
7. A computer program product for determining origins of memory leaks in source code, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by one or more processors, the program instructions executable to: in response to a memory leak being detected, write a first memory dump; search the first memory dump to determine types of suspect leaking collections; create unique identifiers for respective instances of each of the types; in response to a continued memory leak being detected, write a second memory dump; determine which unique identifiers from the second memory dump correspond to growing collection objects of the types; add code to methods of the types of the suspect leaking collections to make the methods uniquely label the respective instances when a next time the methods are called for the respective instances; track code paths of calls that add objects to collections whose identifiers match one of the unique identifiers; and log the code paths for review by developers.
8. The computer program product of claim 7 , further comprising the program instructions executable to:
monitor for signs of the memory leak; and
monitor for signs of the continued memory leak.
9. The computer program product of claim 7 , further comprising the program instructions executable to:
add code to methods of suspect leaking collection types that add objects to a collection instance; and
wherein the code determines whether the collection instance being called matches an identifier of a suspect leaking collection instance.
10. The computer program product of claim 7 , wherein an automated process of determining the origins of the memory leaks requests a target process monitored for the memory leaks to write the first memory dump, wherein the target process writes the first memory dump on storage storing memory dumps and stack traces.
11. The computer program product of claim 7 , wherein an automated process of determining the origins of the memory leaks requests a target process monitored for the memory leaks to write the second memory dump, wherein the target process writes the second memory dump on storage storing memory dumps and stack traces.
12. The computer program product of claim 7 , wherein an automated process of determining the origins of the memory leaks requests a target process monitored for the memory leaks to log the code paths, wherein the target process logs the code paths on storage storing memory dumps and stack traces.
13. A computer system for determining origins of memory leaks in source code, the computer system comprising one or more processors, one or more computer readable tangible storage devices, and program instructions stored on at least one of the one or more computer readable tangible storage devices for execution by at least one of the one or more processors, the program instructions executable to: in response to a memory leak being detected, write a first memory dump; search the first memory dump to determine types of suspect leaking collections; create unique identifiers for respective instances of each of the types; in response to a continued memory leak being detected, write a second memory dump; determine which unique identifiers from the second memory dump correspond to growing collection objects of the types; add code to methods of the types of the suspect leaking collections to make the methods uniquely label the respective instances when a next time the methods are called for the respective instances; track code paths of calls that add objects to collections whose identifiers match one of the unique identifiers; and log the code paths for review by developers.
14. The computer system of claim 13 , further comprising the program instructions executable to:
monitor for signs of the memory leak; and
monitor for signs of the continued memory leak.
15. The computer system of claim 13 , further comprising the program instructions executable to:
add code to methods of suspect leaking collection types that add objects to a collection instance; and
wherein the code determines whether the collection instance being called matches an identifier of a suspect leaking collection instance.
16. The computer system of claim 13 , wherein an automated process of determining the origins of the memory leaks requests a target process monitored for the memory leaks to write the first memory dump and second memory dump, wherein the target process writes the first memory dump and the second memory dump on storage storing memory dumps and stack traces.
17. The computer system of claim 13 , wherein an automated process of determining the origins of the memory leaks requests a target process monitored for the memory leaks to log the code paths, wherein the target process logs the code paths on storage storing memory dumps and stack traces.