Low-overhead run-time memory leak detection and recovery

Electrical computers and digital processing systems: memory – Storage accessing and control – Hierarchical memories

Reexamination Certificate

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

C714S025000, C714S042000, C714S048000

Reexamination Certificate

active

07991961

ABSTRACT:
Leaked memory in a computer system is detected and recovered by first detecting memory leakage within the computer system based on nonlinear and non-parametric time-series regression analysis of software telemetry data generated by one or more software process running on the computer system. If existence of memory leakage is detected, then memory that has leaked is specifically identified and recovered. This is done by halting one or more of the software processes, generating a core image file or files of the halted software process(es), and re-starting the halted process or processes without waiting for analysis of the core image file(s). Then, the core image file is evaluated to specifically identify leaked memory in the computer system based on the core image file. Finally, the identified leaked memory is recovered.

REFERENCES:
patent: 6629266 (2003-09-01), Harper et al.
patent: 7100079 (2006-08-01), Gross et al.
patent: 2004/0205399 (2004-10-01), Wang et al.
patent: 2005/0114844 (2005-05-01), Betancourt et al.
patent: 2006/0080364 (2006-04-01), Lake
Gross, Kenny C. et al., Proactive Detection of Software Aging Mechanisms in Perfermance Critical Computers, 2002.
Benson, Robert, Identifying Memory Management Bugs Within Applications Using the libumem Library, Jun. 2003.
Sun Microsystems, Inc., Solaris Modular Debugger Guide, May 2002.
Tsai, Timothy, Low-Overhead Run-Time Memory Leak Detection and Recovery, 2006.
Goetz, Brian, “Java theory and practice: A brief history of garbage collection,” IBM Corporation, developerWorks, Oct. 28, 2003, 6 pages, http://www-128.ibm.com/developerworks/java/library/j-jtp10283/ (accessed Jan. 14, 2008).
Goettler, Henry et al., “When a Customer Escalates . . . ,” Service and Support Professionals Association (SSPA), Nov. 18, 2003, 2 pages, http://www.thesspa.com/sspanews/111803/article3.asp (accessed Jan. 14, 2008).
Adam Leventhal's Weblog, Jul. 13, 2004, 5 pages, http://blogs.sun.com/ahl/entry/solaris—10—top—11—20.
“Finding memory leaks on Solaris systems,” Blog O'Matty, Feb. 19, 2006, 3 pages, http://prefetch.net/blog/index.php/2006/02/19/finding-memory-leaks-on-solaris-systems/.
“OpenSolaris Community: Modular Debugger (MDB),” Sun Microsystems, Inc., Sep. 27, 2006, 2 pages, http://www.opensolaris.org/os/community/mdb/ (accessed Jan. 14, 2008).
Tsai, Timothy et al., “Low-Overhead Run-Time Memory Leak Detection and Recovery,” 12th Pacific Rim International Symposium on Dependable Computing (PRDC'06), Dec. 18-20, 2006, 9 pages.
“Slab allocation,” Wikipedia, Oct. 7, 2007, 3 pages, http://en.wikipedia.org/w/index.php?title=Slab—allocation&oldid=162763551 (accessed Jan. 14, 2008).
“Garbage collection,” Wikipedia, Oct. 10, 2007, 7 pages, http://en.wikipedia.org/w/index.php?title=Garbage—collection—%28computer—science%29&oldid=163514734 (accessed Jan. 14, 2008).
“Regression analysis,” Wikipedia, Oct. 13, 2007, 8 pages, http://en.wikipedia.org/w/index.php?title=Regression—analysis&oldid=164309249 (accessed Jan. 14, 2008).

LandOfFree

Say what you really think

Search LandOfFree.com for the USA inventors and patents. Rate them and share your experience with other people.

Rating

Low-overhead run-time memory leak detection and recovery does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Low-overhead run-time memory leak detection and recovery, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Low-overhead run-time memory leak detection and recovery will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFUS-PAI-O-2760905

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.