Tracking Down a Freaky Python Memory Leak (Part 2)
If you read part 1 of this series, you know that my crawler was plagued by several memory leaks. Using umdh, I was able to determine that lxml was the culprit. That's a start! But why did those leaks occur in the first place? And how could I fix them? In this second and final post of the series, you'll find out how I used a combination of techniques and tools to analyze and resolve memory leaks in
Tracking Down a Freaky Python Memory Leak
"I thought that memory leaks were impossible in Python?", I said to myself, staring incredulously at my screen. It was 8:00 PM. The memory use of my crawler was slowly, but steadily increasing. As I hadn't changed any significant portion of my code, this made no sense at all. Had I introduced a new bug? If so, where was it? Here follows the full story of how I tracked down a memory leak in my Pyth
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
