James,

I am getting a crash on a capture operation of a single package file. This same package file has been captured at least 6 times to this same archive.

This appears to be the crash that we have discussed before...where it is tripping over the icon cache...but the thing that is odd here is that only the one icon for the package file is displayed in the dialog during the capture...yet it seems to be failing after 10 minutes or so...on one of the components within the package file...so I do not see how this is possible.

The crash log is attached.

Thanks

GKG

Gary K. Griffey wrote:This appears to be the crash that we have discussed before...where it is tripping over the icon cache...

In this case, it's not the same problem. QRecall is crashing trying to handle a fatal exception encountered while reading a file. It tries to read the file, fails, tries again, gives up, and then begins the process of aborting the capture of the file and reporting the problem—that's when it crashes.

What I don't know is if it had a chance to log the root cause of the problem before the crash. Please send a diagnostic report (Help > Send Report...) to answer that question.

Ok...

The report has been sent....

Thanks,

GKG

James,

Ok...I loaded the new version...ran the capture...it crashed again...I then sent a report.

Thanks,

GKG

It looks like we finally nailed this bad boy!

Anyone who wants to test this fix can download QRecall 1.2.0a52.

The bug would randomly manifest itself when recapturing large files (like disk images) that happened to be an even multiple of 3,145,728 bytes (3MB) long, with shifted quanta detection cranked up.

Its workin' like a champ...even Growl!

Thanks...