LogKext using 99% CPU power on MacBook Pro/10.5.2

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by figster...@gmail.com on 16 Mar 2008 at 8:38

Attachments:

• LogKext_error.txt

[GoogleCodeExporter]

Woops, I have a correction. The logKextDaemon works just fine. However, when 
using the LogKextClient, even 
when quitting Terminal, LogKextClient does not quit and starts using 100% CPU 
power. That is my problem - I 
was not using the "quit" command before closing the window. Nevermind this 
issue, it is irrelevant now.

Original comment by figster...@gmail.com on 16 Mar 2008 at 9:59

[GoogleCodeExporter]

Hrm, weird, I can't imagine why logKextClient wouldn't quit when you quit 
Terminal.  Oh crap, I just reproduced 
it!  This is a bug.  Thanks for the report.

Original comment by drspring...@gmail.com on 20 Mar 2008 at 4:29

[GoogleCodeExporter]

Original comment by drspring...@gmail.com on 20 Mar 2008 at 4:29

• Changed state: Accepted

[GoogleCodeExporter]

i have the same problem..... the end result is it makes my computer damn slow 
and
have to use "sudo kill" to bring my mac buck to normal. Has this been addressed 
in
version 2.2 or are you still working on an update???

Original comment by cam_...@hotmail.com on 8 Jun 2008 at 10:57

[GoogleCodeExporter]

ok....

Latest version 2.2.

Using 10.5.3 with a 2.16 Core 2 Duo and 1.5 Gb of ram...

Basically the logkext bit that records the uses so much CPU that i have to "sudo
kill" it...

is that all you needed?

Original comment by cam_...@hotmail.com on 26 Jun 2008 at 9:07

[GoogleCodeExporter]

I'm having the same issue with 10.5.4

Original comment by michaelmiller on 4 Jul 2008 at 5:57

[GoogleCodeExporter]

Fixed in svn, r14

Original comment by drspring...@gmail.com on 12 Jul 2008 at 1:28

• Changed state: Fixed