Microsoft .NET Framework の自動メモリ管理 Part I
SUMMARYGarbage collection in the Microsoft .NET common language runtime environment completely absolves the developer from tracking memory usage and knowing when to free memory. However, you'll want to understand how it works. Part 1 of this two-part article on .NET garbage collection explains how resources are allocated and managed, then gives a detailed step-by-step description of how the garbag
)
Microsoft .NET Framework の自動メモリ管理 Part Ⅱ
ガベージコレクション入門: Microsoft .NET Framework の自動メモリ管理 Part II *Garbage Collection, Part 2: Automatic Memory Management in the Microsoft .NET Framework (December 2000 Vol.15 No.12)* Jeffrey Richter Jeffrey Richter は、『Programming Application for Microsoft Windows』 (Microsoft Press刊、1999 年) の著者で、ソフトウェアコンサルティングおよび教育の会社Wintellect（http://www.Wintellect.com ）の共同設立者でもある。Microsoft .NETプラットフォームとWin32をターゲットとするシステム
実践的なパターン: テストの容易性を高める設計
Considering this sample, here's the worst case scenario for the eleventh GC. Say the tenth Gen 0 collection finished at the beginning of the second interval and the eleventh Gen 0 collection finished at the end of the third interval. That means the time between the end of the two collections is about two sampling intervals, or two seconds. The % Time in GC counter shows 3 percent, and so the eleve
マネージ コードでのメモリ リークの識別と回避
Code download available at: Memory Leaks 2007_01.exe(163 KB) Contents Memory in .NET Applications Checking for Leaks Leaking Stack Memory Leaking Unmanaged Heap Memory "Leaking" Managed Heap Memory Conclusion The first reaction many developers have to the idea of memory leaks in managed code is that it's not possible. After all, the garbage collector (GC) takes care of all memory management, right
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Microsoft Q&A