Bug 659117 - Extremely Poor Performance - Accepting Meeting Invitations
Summary: Extremely Poor Performance - Accepting Meeting Invitations
Keywords:
Status: CLOSED DUPLICATE of bug 659115
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-01 23:17 UTC by David Le Sage
Modified: 2010-12-02 07:32 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-02 07:32:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Le Sage 2010-12-01 23:17:13 UTC
Description of problem:
Evolution is being used as a Zimbra client.  If the user is sent more than one meeting invitation in quick succession, accepting them can lead to severe system performance problems. 


Version-Release number of selected component (if applicable):
Evolution 2.32.1-1.fc14 (64 bit)

How reproducible:
Every time.

Steps to Reproduce:
1. Evolution is being used as a Zimbra email client.
2. A colleague sends two invitations in quick succession, one to book a meeting and the second to update the time of that meeting.
3. Click on the first invitation to open it and hit the "accept" button.  (It is normally a little sluggish at this stage but bearable.)
4. Move down to second email and hit the "update" button.
  
Actual results:
Severe performance detriment on entire system.  Evolution becomes extremely unresponsive for several minutes and other applications are affected.

Expected results:
Much better responsiveness.

Additional info:
This is probably related to the issue with Evolution Calendar performance I logged as https://bugzilla.redhat.com/show_bug.cgi?id=659115

Comment 1 Milan Crha 2010-12-02 07:32:25 UTC
Thanks for a bug report. I agree with the last comment, thus I'm marking this as a duplicate of the older bug.

*** This bug has been marked as a duplicate of bug 659115 ***


Note You need to log in before you can comment on or make changes to this bug.