Unfortunately there isn't. I had this problem back in June and it can occur in a number of ways but the most common ones are 1) Corrupted Calendar entry (usually froma migration from Exchange) and 2) A very large Calendar.
The second instance has been fixed in the latest lightning Nightly build, Lightning was not releasing the old calendar info from memory when it refreshed the calendar therefore when it refreshed every 60 minutes (default) it would eventually eat up all the ram and CPU your computer had.
The first seems to stem from how a calendar entry is formatted by Outlook and wreaks havoc when trying to retrieve the ical version that was migrated to Zimbra.
Because we all can't be geniuses, I'll go first.