iCal is generally sluggish, very noticeably slower than usual. biggest problem is when i want to move or delete recurring events. i have a number of recurring events that i have to manage, either get rid of them or move them, and every time i do this iCal hangs and i have to force quit.
i believe this behaviour is more recent then my upgrading to 10.5.4 - but it could very well have started when i went to 10.5.4 - not sure.
help?
MacBook Pro 2.4gHZ intel core duo 2mb RAM,
Mac OS X (10.5.4)
Hi,
Something does seem to have gone horribly wrong around 10.5.4/3.0.3 which may explain the problem you are seeing. I have had problems with iCal and SyncServer gobbling up CPU time and being slow, especially when syncing with an iPhone. You can use Activity Monitor to see if you have problems like this. This was the prelude to a problem described in the thread "iCal will not save my events, appointments..." so be aware that you may also have this issue. Because events are not being saved you may not be aware of the problem if you never restart iCal or the Mac.
Best of luck,
Gordon.
iCal is definitely saving my info. but its terribly sluggish.
another weird thing, besides being unable to delete or move recurring events, is that occasionally when syncing with mobileme, it will re-import something i've recently deleted. as if my iCal is not the master. but then other times, it behaves and does not re-import previously sync'd info. very inconsistent.
Macrumors is reporting that the release of 10.5.5 is getting closer, it will be best to wait until that is out before digging any further.
here's hoping!
I had the same problem, with slow iCal response and frequent crashes, increasing in frequency over several months. It finally came to a head when I tried to delete a recurring event. Every time, iCal hung and crashed; I had to force quit. I tried several approaches to deleting (delete all instances, delete only one instance, delete in day view, delete in week view, etc.). None worked.
I solved the problem by using terminal. First I made a backup of my iCal workspace from within iCal using the Backup menu option. Then I navigated to the event in question (the bad recurring event) using the unix "cd" command.
For example, if you saved your iCal backup in the following directory:
/Users/charlie/Backups/
under the name "iCal 2008-12-11.icbu" then type the following command into Terminal:
cd /Users/charlie/Backups/iCal\ 2008-12-11.icbu
then type
"cd Calendars"
then type "ls"
you should see a list of all your calendars with cryptic names
e.g., 1234A9F-3F.calendar
you need to figure out which of these calendars has the corrputed event
navigate one directory down into each of these calendars and type
cat Info.plist
near the bottom of the output will be the name of the calendar (e.g., "Holidays" or "Personal").
Once you have found the calendar that contains the corrupted event, navigate one directory further down by typing
cd Events
then type
ls -l | sort
chances are the corrupted event will be the one at the very bottom of your screen and should have a very large block size compared to the next event up. You can check this by typing
cat 34F5-1234.ics (or whatever the filename is)
and making sure that the text matches the corrupted event's text
Now delete the corrupted event (although you might want to copy the text to a text file first if it has important information in it that you want to re-enter at a later date)
e.g., type
rm 34F5-1234.ics
Now relaunch iCal, and choose "restore" from the file menu. Pick the backup that you have just modified by deleting the corrupted event.
It took my backup about 5 minutes to reload and my laptop's fan turned on during this time, almost seemingly like it was going to hang again. But it did not. And my sluggish performance was gone.
P.S. I guess there is nothing in the above set of actions that needs Terminal. You can do it all with your mouse from the Finder. You will need to control-click on the ".icbu" iCal backup file to get it to open like a directory ("Show package contents").
