Le mercredi 26 novembre 2008 à 08:31 +1100, Michael Ashley a écrit : > Hi Matthias, > > > the debug output is perfectly normal behaviour. It is displayed on > > each frame that cannot be displayed because there is no widget to > > show. > > I don't know the details of the code, but one wonders whether it is > necessary to poll 30 times a second. > > > However 50% CPU is not. Actually I cannot reproduce this, > > when I have the widget unrealized and am getting this trace output, > > all I get is CPU load of 1-2%... > > Is there anything special you do? Just preview and deactivated call view? > > The eee PC 901 has an inbuilt camera that can be deactivated to save > power. If I turn off the camera, and then start ekiga, the CPU load > stays at 50% until the call view panel is displayed. > > Actually I just did some more tests and it isn't quite that simple! I > only get the CPU problem if, in a previous invocation of ekiga I was > displaying images from the camera. If I then deactivate the call > view frame, exit ekiga, turn off the camera, and restart ekiga, _then_ > I see the 30 errors/second and 50% CPU.
If there is no debug output, do you also reach 50% CPU in the same situation ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
