Советы по поиску и отладке заброшенной памяти и роста кучи

I recently watched one of the WWDC 2010 videos: Session 311 - Advanced Memory Analysis with Instruments. The link is here.

There is an interesting example in the video on finding Abandoned Memory. They say that it is often more important to debug than leaks but can be more difficult.

Abandoned Memory is defined as "Accessible allocated memory that is never used again".

A leak is defined as "Allocated memory that can no longer be reached."

The primary way to find Abandoned Memory is to take heap shots using the Allocations instrument.

However, after determining that I have abandoned memory in my code, I have found that it is really difficult to find out exactly where it is coming from.

I am looking for some good tips or resources for finding Abandoned Memory.


7 голосов | спросил Jonah 25 +04002010-10-25T07:14:52+04:00312010bEurope/MoscowMon, 25 Oct 2010 07:14:52 +0400 2010, 07:14:52

0 ответов

Похожие вопросы

Популярные теги

security × 330linux × 316macos × 2827 × 268performance × 244command-line × 241sql-server × 235joomla-3.x × 222java × 189c++ × 186windows × 180cisco × 168bash × 158c# × 142gmail × 139arduino-uno × 139javascript × 134ssh × 133seo × 132mysql × 132