When qrecall encounters a full disk during capture it will not stop. The capture ran overnight and the progress indicator was at the same position I left it 6 hours sooner.

The log indicates qrecall encountered a full disk and stopped processing. However, the application was still running and would not Quit. I performed a Force Quit, but the qrecall Activity Monitor showed that qrecall was still running.

Qrecall would also not attempt to continue after I trashed some large files in order to give it some more space.

I ended up logging out and back in and then trashed the quanta file.

I'm running a Trial key before purchasing. I really like the concept behind qrecall, but this is a negative indicator to me.

Maybe v1.2 will provide a fix?

Mike Haire wrote:When qrecall encounters a full disk during capture it will not stop. The capture ran overnight and the progress indicator was at the same position I left it 6 hours sooner.

That's odd. QRecall is usually extremely (some would say too sensitive) to disk full conditions. It actually goes out of its way to detect a disk full condition before it actually happens, so it can finish up in an orderly fashion.

The log indicates qrecall encountered a full disk and stopped processing.

Please send a diagnostic report (Help > Send Report). This will help let me review the actual log messages and try to determine what happend.

However, the application was still running and would not Quit. I performed a Force Quit, but the qrecall Activity Monitor showed that qrecall was still running.

The QRecall application is not the process that performs the QRecall actions. The heavy lifting is performed by a process named QRecallHelper. QRecall (the application) and the QRecall monitor window are just pretty faces to what's going on behind the curtain. To really kill a QRecall action that's running launch the Activity Monitor, find the QRecallHelper process, and kill that.

Qrecall would also not attempt to continue after I trashed some large files in order to give it some more space.

It's hard to say what's going on. If the QRecallHelper process was still running and had the archive files open, another QRecall action won't start until the first one is finished.

I ended up logging out and back in and then trashed the quanta file.

That will also kill the background helper process.

I'm running a Trial key before purchasing. I really like the concept behind qrecall, but this is a negative indicator to me.

Glad to have you aboard. Let's see if we can figure out what's going on and get you on track.

Maybe v1.2 will provide a fix?

The beta version has a lot of improvements over the current released version, some of which have to do with how QRecall deals with disk full situations. Since you're just starting out, it certainly wouldn't hurt to give the beta a spin.

Hello, James:

Thanks for the quick response! I've downloaded the beta and will test drive it. Of course, my first test will be to recreate this scenario.