Cork: dynamic memory leak detection for garbage-collected languages

@inproceedings{Jump2007CorkDM,
  title={Cork: dynamic memory leak detection for garbage-collected languages},
  author={Maria Jump and Kathryn S. McKinley},
  booktitle={POPL},
  year={2007}
}
A memory leak in a garbage-collected program occurs when the program inadvertently maintains references to objects that it no longer needs. Memory leaks cause systematic heap growth, degrading performance and resulting in program crashes after perhaps days or weeks of execution. Prior approaches for detecting memory leaks rely on heap differencing or detailed object statistics which store state proportional to the number of objects in the heap. These overheads preclude their use on the same… CONTINUE READING
Highly Influential
This paper has highly influenced 12 other papers. REVIEW HIGHLY INFLUENTIAL CITATIONS
Highly Cited
This paper has 101 citations. REVIEW CITATIONS

Citations

Publications citing this paper.

101 Citations

01020'09'12'15'18
Citations per Year
Semantic Scholar estimates that this publication has 101 citations based on the available data.

See our FAQ for additional information.

References

Publications referenced by this paper.
Showing 1-2 of 2 references

Java Memory Leaks – Catch Me If You Can: Detecting JavaLeaks using IBM Rational Application Developer 6.0

  • S. C. Gupta, R. Palanki
  • Technical report,
  • 2005
Highly Influential
5 Excerpts

Sevitzky. LeakBot: AnAutomated andLightweight Tool for Diagnosing Memory Leaks in Large Java Applications

  • N. Mitchell andG
  • In ECOOP 2003 –Object Oriented Programming: 17th…
  • 2003
Highly Influential
5 Excerpts

Similar Papers

Loading similar papers…