Wesley Lin

> i.e. you could most likely put any code there (e.g. sleeping for 1ms) and you'll see the memory usage increase. YES, I have tried as you said. The point...

If I call `torrent_file()` or other high-cost procedures in read_piece_alerts handler, it may cause that the current generation alerts have a longer life(before clean) than before. Which also causes the...

For now, I just forbid the read-piece actions when torrent is under checking-files state to prevent the case.

I see, the more number of pieces I keep in RAM at a time, the more memory usage it takes at a time, that is right. What I don't understand...

I try to look into this problem again recently, I found that, if I do lots of read_piece during file-checking, the size of `read_lru1` list in block_cache will be pretty...

two parts, `read_piece_alerts` holds some memory, and the block_cache holds another part. according to the code, it seems only when move piece to the ghost list has the max_size, the...

I monitor the cache list size during test. by default the list size is 32, but the lru1 size increases to thousands and not be released after all actions done.

file1_dump ``` 0000000: 6865 6c6c 6f20 776f 726c 640a 0a20 0a hello world.. . ``` run `xxd -r file1_dump file1` can produce the file1 file2_dump ``` 0000000: 6865 6c6c 6f20...