IP Library Granted Patent US 7,895,483
Granted Patent B2
US 7,895,483 · App. 11/753,899 · Granted Feb 22, 2011

Software memory leak analysis using memory isolation

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,895,483
App. No.
11/753,899
Granted
Feb 22, 2011
Kind
B2
Abstract

A computerized method, program product, and a service that allocates and isolates leaky memory during the execution of an application in a data processing system. A memory controller having several components first identifies a leaky section of memory and delegates to an allocation component to allocate more memory if possible. If, however, the problematic memory section should not be allocated more memory, an isolator component can isolate the memory section and further divide the memory section into subsections and so on. Each section and each subsection may then be tested to determine if more memory can be allocated, tested to determine if memory resources are strained so as to identify the application or its component causing the strain and then binding the memory. Each section and subsection and further divided and isolated until the leaky portion of memory is identified, and as a result, the software component causing the leak can also be identified. The software component associated with the leaky memory section or subsection can also be taken out-of-service.

Claims (25)

1. A method of finding a source of an abnormal memory condition in a data processing system, the method comprising the steps of:

recursively logically dividing, by a control computer, a memory section experiencing the abnormal memory condition into a plurality of smaller logical memory sections; and

recursively testing, by the control computer, the plurality of smaller logical memory sections until one or more of the smaller logical memory sections is determined to be the source of the abnormal memory.

2. The method of claim 1 , further comprising:

allocating, by the control computer, more memory to the smaller logical memory section experiencing the abnormal memory condition.

3. The method of claim 1 , further comprising:

isolating, by the control computer, the smaller logical memory section experiencing the abnormal memory condition so that more memory resources are not allocated to the smaller logical memory section;

identifying, by the control computer, a logical component associated with the smaller logical memory section experiencing the abnormal memory condition.

4. The method of claim 3 , further comprising:

issuing, by the control computer, a warning that the smaller logical memory section is experiencing an abnormal memory condition and the logical component is associated with the abnormal memory condition.

5. The method of claim 3 , further comprising:

binding, by the control computer, the logical component to the smaller logical memory section experiencing the abnormal memory condition.

6. The method of claim 5 , further comprising:

taking, by the control computer, the logical component out-of-service.

7. The method of claim 1 , wherein the control computer is connected to the data processing system is over a network.

8. The method of claim 1 , wherein the memory of the data processing system is connected to the data processing system over a network.

9. A computer program product for identifying a logical component of an executing application creating an abnormal memory condition in a data processing system, the computer program product comprising:

computer-readable tangible storage device;

first computer usable program code, stored on the computer-readable tangible storage device, to identify a section of memory experiencing the abnormal memory condition and logically partition the identified memory section into one or more logical subsections;

second computer usable program code, stored on the computer-readable, tangible storage device, to recursively test each of the one or more logical subsections to determine if the one or more logical subsections is low on memory;

third computer usable program code, stored on the computer-readable, tangible storage device, to recursively test each of the one or more logical subsections to determine if the one or more logical subsections has strained memory resources; and

fourth computer usable program code, stored on the computer-readable, tangible storage device, to recursively test each of the one or more logical subsections to determine if the one or more logical subsections is leaking memory.

10. The computer program product of claim 9 , further comprising fifth computer usable program code, stored on the computer-readable, tangible storage device, to allocate more memory to the one or more logical subsections of memory experiencing the abnormal memory condition.

11. The computer program product of claim 9 , further comprising sixth computer usable program code, stored on the computer-readable, tangible storage device, to bind an application component causing the abnormal memory condition and the one or more logical subsections of memory experiencing the abnormal memory condition.

12. The computer program product of claim 9 , further comprising seventh computer usable program code, stored on the computer-readable, tangible storage device, to take the one or more logical subsections of memory experiencing the abnormal memory condition out-of-service from the data processing system.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2019
From: INTERNATIONAL BUSINESS MACHINES CORPORATION
To: WRP IP MANAGEMENT, LLC
Reel/Frame 049033/0410 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 9, 2007
From: HOGSTROM, MATT RICHARD; MINSHALL, ROBBIE JOHN
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 019530/0273 →