Bug 291801 - KMail hangs in a futex call
Summary: KMail hangs in a futex call
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-17 18:41 UTC by Daniel Vrátil
Modified: 2017-01-07 22:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Vrátil 2012-01-17 18:41:55 UTC
Version:           4.8 (using Devel) 
OS:                Linux

When I try to open INBOX on an IMAP account KMail hangs. Strace
shows that it always hangs in a futex call.

I think it is caused by a race condition because when I run KMail
in strace, I'm unable to reproduce the issue (it's obviously running slower).
It only happens when I run KMail on it's own, strace -p `pidof kmail` of 
the frozen KMail then shows

$ strace -p `pidof kmail`
Process 5672 attached - interrupt to quit
futex(0x7f546fcac8a0, FUTEX_WAIT_PRIVATE, 2, NULL


It happens only with INBOX, other folders can be opened and I can switch
between emails. It freezes sometimes when I switch between emails to 
quickly (but only sometimes, does not seem to be regular).

Let me know if you need any more information.

Reproducible: Sometimes

Steps to Reproduce:
1) run KMail with IMAP account
2) open INBOX
3) KMail freezes
4) strace -p `pidof kmail` will show it hangs in futex()

Actual Results:  
KMail freezes

Expected Results:  
KMail should not freeze :)
Comment 1 Denis Kurz 2016-09-24 18:07:30 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:28:01 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.