ok, I downloaded and installed the latest version of Daylite Suite onto my Macbook running OS X 5.4. The installation went ok, but this app crashes every single time I run it. It starts ok, and lets me get as far as entering a contact or an opportunity or something, but never less than a few minutes later I will do something (quit mail, add a contact, an opportunity, or whatever) and I get the beachball and Daylite shows up as Not Responding in the activity monitor.

I've been through the checklist on the stick at the top of this group, and fixed a few things and rebooted. No change. I went through the knowledgebase, and the only relevant post I could find was on mail bundles. I have none.

Before I abandon this, does anyone have any ideas? I like the looks of the software, but it has to work for more than 5 minutes before I'll even think about buying it.

Thanks!

Steve

If you haven't already, try the latest 3.7.5 beta here.

If it still crashes, it should normally bring up a window to report the crash. If it still doesn't do that, please do the following:

Whenever Daylite comes up as 'Not Responding', load up Activity Monitor (from the Finder: Go > Utilities and open Activity Monitor), make sure you have 'All Processes' set for 'Show' and nothing typed into the Filter field, then select Daylite from the list below (should come up in red), then click Sample Process in the toolbar. Once the sampling is done, please save it and send it in to our Support team (support at marketircle) with a short description of the problem you're encountering.

Ok, I will do that. However, after disabling Plaxo, Spanning Sync, and Weatherbug, I haven't had a crash. Not sure whether Daylite's worth having to disable 3 other tools, but it seems to have removed the problem.

We usually recommend that you setup sync between Daylite - AB/iCal before you bring in other external sources (including .Mac/Mobileme) to make sure the sync is working as you want.

I doubt Weatherbug would be related, but the others might. However, Daylite might not necessarily be the culprit, as it could be Sync Services having trouble doing the sync from multiple sources; only after seeing a crash report could we be sure of the exact cause of any crash.