thanks, we'll look into it. I suggest you add *.chm to the exclusion filters as chm unpacking code in clamav-release is quite buggy. Archivers support is improved in clamav-devel but it will take some time before the devel tree is merged into release.

anyway if you find the file that crashes clamscan I would happy to have it

The problem is - it doesn't look like the specific file. I've got a directory full of chm files. It crashed half-way through this directory on full C: scan.
But when I tried scanning this directory manually - no problem.

looks like chm scanning doesn't close handles properly and it runs out of avaialble file handles (we dealt with similar problems before)