GNOME Bugzilla – Bug 581019
ekiga 3.2 freezing by using the voip sip client on 100% cpu usage
Last modified: 2013-02-12 23:22:41 UTC
Steps to reproduce: 1. its freezed by using the voip sip account sparvoip.de on ubuntu 9.04 2. 3. Stack trace: Other information:
Could you please execute it through gdb, instructions are at http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash
Peter, any news?
hi, sorry my english is not that good. i using ekiga every day, but only the sip account and ekiga using to much cpu, between 90-100%, so when other programms opened, freezing my computer. when i use only ekiga -other prgramms closed- than works, but cpu is always 90-100%! (ubuntu 9.04) in the version ekiga 2.xx, ubuntu 8.10 was the cpu usage by 35-45%. greetings peter
Does it uses 100% cpu only when communicating, or always? If you do not have video preview enabled (if you do not see any image), does it still uses 100% cpu?
yes, i don't use the video client have only login by the sip account, have no ekiga account ore something else. the cpu going up to 100% when the other site pick up the phone, so only by communicating.
I think you have an old computer, or you use now a codec which needs more processing power (CPU) than before, or there is a driver problem, so I would be tempting to close this bug...
Hmmm... it's not normal that the cpu usage went that way up :-/
At the risk of saying me too, I have the same problem. I am running on a HP 6730b with 2G RAM and Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz CPU. I suppose that is not a small configuration. I discovered after some tests that's the Input Device choice that influence greatly the CPU usage: if I use Default (PTLIB/ALSA) then I have around 100% used (1 core out of 2). I put something else (SILENT(Ekiga/Ekiga) or HDA(PTLIB/ALSA)) then the CPU usage is around 8% (but for some reason with HDA I don't have the sound). If I also add --- (Gstreamer/Alsa) as output device then the CPU skyrocket to nearly 200% for the ekiga process
Matthieu: wouldn't it be an ALSA bug in that case ? (ALSA taking the CPU)
Damien: how can I know ? I suppose by profiling ekiga we can understand where it is spending time but I have no clue on how to do it ...
Do you have this high CPU problem when you use pulse as sound manager? See also bug #600623.
Hi Eugen, Sorry for the delay. so removing the pulseaudio do help (but ekiga is still eating 30/50% for CPU). But not using pulse I'm facing quite often (on the second call) the fact that output volume in ekiga is at 0 and I have no way to increase it.
Hi All, As a note to this I've had similar reports on Fedora but never been able to recreate them myself. I'm not sure if its a particular kind of sound card, or registrar or gateway or even something like an address book that causes the problem as I've not been able to get enough debug or enough time to chase to try and narrow things down. I've had reports on it for both ekiga 3.0.x and 3.2.x
About the high CPU usage problem: Do you have the same problem both when using the Default ALSA audio device (DMIX access) AND the other available device (Direct Access to the soundcard)?
Damien, Sorry I'm not expert enough to test what do you propose. Do you have a simple test plan (ie. like do this do that,change this change that). For the moment my ekiga is using Default PTLIB/ALSA.
What other choices do you have except "Default (PTLIB/ALSA)" in the drop-down menu?
So I have HDA Intel (PTLIB/ALSA), Silent, /dev/dsp (PTLIB/OSS).
Try "HDA Intel" and see if the CPU usage is as high as when using "Default".
A downstream bug report with a gdb log https://bugzilla.redhat.com/show_bug.cgi?id=551123
*** Bug 625387 has been marked as a duplicate of this bug. ***
Does this still appear with ekiga >= 3.9.90?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!