Bug 871517 - Again evolution stuck on close
Summary: Again evolution stuck on close
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-30 15:23 UTC by Mikhail
Modified: 2012-10-31 07:16 UTC (History)
3 users (show)

Fixed In Version: evolution-ews-3.6.0
Clone Of:
Environment:
Last Closed: 2012-10-31 07:16:57 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
backtrace for evolution (10.77 KB, text/plain)
2012-10-30 15:24 UTC, Mikhail 		no flags Details
backtrace for evolution-addressbook-factory (3.00 KB, text/plain)
2012-10-30 15:25 UTC, Mikhail 		no flags Details
backtrace for evolution-calendar-factory (3.97 KB, text/plain)
2012-10-30 15:26 UTC, Mikhail 		no flags Details
View All

Description Mikhail 2012-10-30 15:23:43 UTC 
Description of problem:
Again evolution stuck on close
Comment 1 Mikhail 2012-10-30 15:24:28 UTC 
Created attachment 635658 [details]
backtrace for evolution
Comment 2 Mikhail 2012-10-30 15:25:28 UTC 
Created attachment 635659 [details]
backtrace for evolution-addressbook-factory
Comment 3 Mikhail 2012-10-30 15:26:05 UTC 
Created attachment 635660 [details]
backtrace for evolution-calendar-factory
Comment 4 Milan Crha 2012-10-31 07:16:57 UTC 
Thanks for a bug report. The two factories are idle, the whole "freeze" is on the evolution side. The EWS account is disposing in one thread, waiting for its soup-thread to finish, while two other threads are using the same connection like it was alive.

I suppose this is fixed in Fedora 18, evolution-ews 3.6.0+, where the internals of connect and disconnect had been rewritten significantly. I'm closing this in favour of Fedora 18, but please re-evaluate when it's available and feel free to reopen, if you'll face it there too.
Note You need to log in before you can comment on or make changes to this bug.