Comment 24 for bug 69752

I just saw the same crash while downloading an 85Mb .mp3 file using Azureus (bittorrent client):

strace -p on the active /usr/lib/beagle/IndexHelper.exe thread shows:

fstat64(31, {st_mode=S_IFREG|0644, st_size=86537920, ...}) = 0
_llseek(31, 13018790, [13018790], SEEK_SET) = 0
read(31, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192

fstat64(31, {st_mode=S_IFREG|0644, st_size=86537920, ...}) = 0
_llseek(31, 13018791, [13018791], SEEK_SET) = 0
read(31, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192

fstat64(31, {st_mode=S_IFREG|0644, st_size=86537920, ...}) = 0
_llseek(31, 13018792, [13018792], SEEK_SET) = 0
read(31, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192

over and over. I stopped the strace after gathering a million or so lines of output, and nothing had changed. It was still incrementing the offet by one each time, and reading another 8k's worth of zero bytes.

I suppose that each time the torrent client writes to the file, it triggers yet another scan of the incomplete file as well.