Nice catch!

The activity monitor was using the wrong preference value to determine if it should open the window at application startup.

It's all straightened out now, and the fix will show up in the next beta release—which, if everything is working correctly, will appear in the activity window.

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.

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.

Anyone who's experiencing this problem can download this alpha release: QRecall 1.2.0a50.

Good or bad, pleases post your experiences with a50 here, by uploading a diagnostic report (Help > Send Report...), or both.

Gary,

I just checked up on Growl development, and it looks like I can upgrade QRecall from the Growl 1.2 framework to the 1.2.2 framework. Most comments seem to indicate that 1.2.2 works reliably with Growl 1.3 on Lion.

The Growl 1.3 SDK isn't available yet, and doesn't support Leopard, so that isn't an option right now. I'll upgrade the embedded framework this week and it should roll out with the next release of QRecall. Please me know if the behavior changes.

Gary K. Griffey wrote:I purchased the new Growl 1.3 available via the App store for my 10.7.2 machine.

Gary,

I saw the announcement by the Growl Team a few weeks ago that they had produced an App Store version of Growl along with a new SDK for developers. I made a note to update the Growl framework imbedded in QRecall, but haven't gotten around to it just yet.

The latest App Store Growl, however, should work with older Growl compatible software. And for some people, such as Steve, that's clearly the case.

A few Growl developers, however, have commented that sometimes it works and sometimes it doesn't, and there's no clear consensus right now as to why. One thing you might try is to log out and back in again (if you haven't already). The Growl source in QRecall is the monitor process, which starts when you log in and stops when you log out. Note: if you're running the Beta version of QRecall, choose the Windows > Restart Monitor command—you'll get the same effect.

I will note that the old version of Growl uses distributed notifications to communicate. Several users of QRecall have noted that the monitor window sometimes doesn't appear when an action starts. QRecall also uses distributed notifications to announce when actions start and stop. Personally, I think there's something wrong with distributed notifications in Lion.

Gary K. Griffey wrote:Sorry...

No need to appologize. It is a bug in the UI, which I've hopefully fixed for everyone, and will appear in the next version.

If anyone is having similar problems and can't work around it, drop me a message and I'll provide an alpha release to try.

Steve,

There were a couple of subtle Lion-related bugs in the browser interface. I've plugged a couple of them. I don't know if I've gotten them all, but I can no longer reproduce what you reported (both here and in the diagnostic reports you sent).

One thing I did discover is that Lion has broken a number of QRecall features:

The Reveal in QRecall Archive service

The Capture to QRecall Archive service

Searching for an item by opening an archive from a Spotlight search

All of these features depend on information being passed to the application via AppleEvents (the technology on which AppleScripts is built on). In Lion, none of this information is getting passed to the application.

I'm looking into this situation now.

Bruce Giles wrote:Does QRecall (either the current release or the beta) require Spotlight on the backup volume?

No.

QRecall does not have any features that depend on Spotlight indexing its archives—except, obviously, the ability to find items in archives using Spotlight.

Whether you choose to have Spotlight index your archives or not is up to you, but it won't change how QRecall operates.

Bruce Giles wrote:Does QRecall check for updates when the application isn't running? Would it be possible to post an notification of updates in the Activity Monitor window (possibly as a preference, in case some people don't want that)?

Good idea. I've added that to the wish list.

Also, are you documenting the new features yet, and how to use them, anywhere other than in the update notification window?

The notes you see in the update window can also be perused on the beta release notes page, which you can always get to via the download page.

Gary K. Griffey wrote:If I then click on Restart Monitor...the Monitor window opens and works fine. It even works fine on subsequent Actions...until you reboot...then I am forced to perform the manual Restart Monitor once again.

I've received a couple of similar reports. I still haven't been able to duplicate this problem here, but I have no doubts that it's an inter-process communications change introduced in Lion.

I have a plan to address this, but it didn't make it into the latest release.

QRecall 1.2.0(47) beta was just released which fixed the above problem.

If you upgrade from 1.2.0(41) directly to 1.2.0(47), you can ignore the previous post.

And the first bug to surface after rushing a release out the door goes to...

After upgrading to 1.2.0(46) beta, you will need to pre-authorize QRecall in the preferences.

Go to QRecall > Preferences.... In the Authorization tab, click on the Pre-Authorize button. This only needs to be done once. QRecall will remember this preference from there on out.

Gary K. Griffey wrote:The current beta version expired as of 10/01 as is throwing a message upon launch.

My apologies, the latest beta did expire today.

I'll release the next version immediately. If anyone encounters any problems, please send diagnostic reports and/or post the issue to the forum so they can be dealt with quickly.

Steve Mayer wrote:Any timeframe for an updated beta version?

The original plan was to have a release two weeks ago. Unfortunately, the power supply on my RAID tower (used for most of the heavy duty QRecall testing) had other plans.

The RAID tower is back from repairs, I've been putting QRecall through its paces, and I expect to push out the next release within a day or so. The delay has resulted in a particularly hefty release, with lots of new features and fixes.