Bug 141770 - constant deadlocks on changing network connectivity
constant deadlocks on changing network connectivity
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Malcolm
:
Depends On:
Blocks: FC5Target
  Show dependency treegraph
 
Reported: 2004-12-03 12:47 EST by Colin Walters
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-23 13:51:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
evolution backtrace (8.05 KB, text/plain)
2004-12-03 12:48 EST, Colin Walters
no flags Details

  None (edit)
Description Colin Walters 2004-12-03 12:47:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041114 Firefox/1.0

Description of problem:
I swear I filed a bug on this before and we discussed it, but I can't find it.  Anyways, I got a better backtrace from a deadlock.  This seems to happen *very* often now.  Particularly after waking my laptop up from sleep, or changing network connectivity with NetworkManager.

Version-Release number of selected component (if applicable):
evolution-2.0.2-4

How reproducible:
Sometimes

Steps to Reproduce:
1. Use evolution
2. Change network?  Wake from sleep?
  

Additional info:
Comment 1 Colin Walters 2004-12-03 12:48:26 EST
Created attachment 107850 [details]
evolution backtrace
Comment 2 Dave Malcolm 2005-08-22 20:45:20 EDT
Looking at the backtrace, thread 12 is waiting to acquire a lock on an IMAP
backend, thread 6 is trying to grab data via SSL from an IMAP backend, thread 5
is also waiting for a lock on the IMAP backend.

My guess is that thread 6's read will never succeed, since its IP address has
changed from under it. I don't know offhand if this will timeout.

Am I right in thinking that the latest rawhide evolution is a bit more robust in
this regard?
Comment 3 Colin Walters 2005-08-22 21:02:10 EDT
It seems to work much better, yes.  You can probably close this bug.

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