Bug 529504 - using libasyncns leads to constant very high load average
Summary: using libasyncns leads to constant very high load average
Keywords:
Status: CLOSED DUPLICATE of bug 529202
Alias: None
Product: Fedora
Classification: Fedora
Component: libasyncns
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 529202
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-17 21:23 UTC by Matěj Cepl
Modified: 2018-04-11 10:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-19 17:40:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 379452 0 None None None Never

Description Matěj Cepl 2009-10-17 21:23:12 UTC 
Description of problem:
When using (optional) python-libasyncns with gajim my computer takes load average 4.5+ even when gajim is idling for many ours and doing basically nothing

Version-Release number of selected component (if applicable):
libasyncns-0.7-3.fc12
python-libasyncns-0.7.1-3.fc12

How reproducible:
100%

Steps to Reproduce:
1.install python-libasyncns
2.start gajim
3.
  
Actual results:
load average goes to very high level and it stays there

Expected results:
the library is supposed to help

Additional info:
There is an Ubuntu bug for this, not sure what is the upstream of this package
Comment 1 Matěj Cepl 2009-10-17 21:24:21 UTC 
Oh and there is our kernel bug 529202 for this as well. Setting this bug as being blocked.
Comment 2 Lennart Poettering 2009-10-19 17:40:38 UTC 
I looked into this in detail over the weekend and according to strace all workers hang in recv() properly. So there is really nothing libasyncns could actually be doing wrong. Seems to be entirely a kernel issue to me, which I reported in bug 529202.

I'll close this now as duplicate.

*** This bug has been marked as a duplicate of bug 529202 ***
Note You need to log in before you can comment on or make changes to this bug.