[Bug 703329] New: kopete: inducing high load looking for googletalk-call ?
https://bugzilla.novell.com/show_bug.cgi?id=703329 https://bugzilla.novell.com/show_bug.cgi?id=703329#c0 Summary: kopete: inducing high load looking for googletalk-call ? Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers@suse.de ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 I noticed my machine was a bit sluggish. top revealed that kopete was rather busy. I strace'd it and noticed it was absolutely churning. I narrowed it down to this: [pid 3261] --- SIGCHLD (Child exited) @ 0 (0) --- [pid 3261] wait4(4753, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGPIPE}], WNOHANG, NULL) = 4753 [pid 3261] clone(Process 4757 attached child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f6775b2ea30) = 4757 [pid 4757] execve("/home/jnelson/bin/googletalk-call", ["googletalk-call"], [/* 95 vars */]) = -1 ENOENT (No such file or directory) [pid 4757] execve("/usr/local/bin/googletalk-call", ["googletalk-call"], [/* 95 vars */]) = -1 ENOENT (No such file or directory) [pid 4757] execve("/usr/bin/googletalk-call", ["googletalk-call"], [/* 95 vars */]) = 0 [pid 4757] arch_prctl(ARCH_SET_FS, 0x7fd306182720) = 0 [pid 4757] clone(Process 4758 attached child_stack=0, flags=CLONE_PARENT_SETTID|SIGCHLD, parent_tidptr=0x7fff23d22718) = 4758 [pid 4757] wait4(4758, Process 4757 suspended <unfinished ...> [pid 4758] execve("/bin/sh", ["sh", "-c", "stty -echo"], [/* 95 vars */]) = 0 [pid 4758] arch_prctl(ARCH_SET_FS, 0x7f82455a1700) = 0 [pid 4758] execve("/bin/stty", ["stty", "-echo"], [/* 94 vars */]) = 0 [pid 4758] arch_prctl(ARCH_SET_FS, 0x7f983b0e9700) = 0 [pid 4758] exit_group(1) = ? Process 4757 resumed Process 4758 detached [pid 4757] <... wait4 resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], 0, NULL) = 4758 [pid 4757] --- SIGCHLD (Child exited) @ 0 (0) --- [pid 4757] clone(Process 4759 attached (waiting for parent) Process 4759 resumed (parent 4757 ready) child_stack=0, flags=CLONE_PARENT_SETTID|SIGCHLD, parent_tidptr=0x7fff23d22718) = 4759 [pid 4759] execve("/bin/sh", ["sh", "-c", "stty echo"], [/* 95 vars */]) = 0 [pid 4759] arch_prctl(ARCH_SET_FS, 0x7ff242924700) = 0 [pid 4757] wait4(4759, Process 4757 suspended <unfinished ...> [pid 4759] execve("/bin/stty", ["stty", "echo"], [/* 94 vars */]) = 0 [pid 4759] arch_prctl(ARCH_SET_FS, 0x7feecc14f700) = 0 [pid 4759] exit_group(1) = ? Process 4757 resumed Process 4759 detached [pid 4757] <... wait4 resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], 0, NULL) = 4759 [pid 4757] --- SIGCHLD (Child exited) @ 0 (0) --- [pid 4757] clone(Process 4760 attached child_stack=0x7fd3030b6fd0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x7fd3030b79d0, tls=0x7fd3030b7700, child_tidptr=0x7fd3030b79d0) = 4760 [pid 4757] --- SIGPIPE (Broken pipe) @ 0 (0) --- Process 4757 detached [pid 4760] +++ killed by SIGPIPE +++ [pid 3261] --- SIGCHLD (Child exited) @ 0 (0) --- [pid 3261] wait4(4757, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGPIPE}], WNOHANG, NULL) = 4757 [pid 3261] clone(Process 4761 attached (waiting for parent) Process 4761 resumed (parent 3261 ready) child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f6775b2ea30) = 4761 [pid 4761] execve("/home/jnelson/bin/googletalk-call", ["googletalk-call"], [/* 95 vars */]) = -1 ENOENT (No such file or directory) [pid 4761] execve("/usr/local/bin/googletalk-call", ["googletalk-call"], [/* 95 vars */]) = -1 ENOENT (No such file or directory) [pid 4761] execve("/usr/bin/googletalk-call", ["googletalk-call"], [/* 95 vars */]) = 0 *Why* is kopete trying, over and over and over again, to execute googletalk-call? It probably ought to check at startup, or perhaps limit itself to once a minute or something. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=703329 https://bugzilla.novell.com/show_bug.cgi?id=703329#c1 --- Comment #1 from Jon Nelson <jnelson-suse@jamponi.net> 2011-08-21 03:19:52 UTC --- Still a problem (and a serious one!, it drives my CPU temp up and my battery life down) with 4.7.whatever. I'm running Tumbleweed now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=703329 https://bugzilla.novell.com/show_bug.cgi?id=703329#c2 Hrvoje Senjan <hrvoje.senjan@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |hrvoje.senjan@gmail.com Resolution| |FIXED --- Comment #2 from Hrvoje Senjan <hrvoje.senjan@gmail.com> 2012-11-15 22:03:45 UTC --- Closing, 11.4 reached EOL, if you can reproduce with >= 12.1 open a new BR. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com