[asterisk-bugs] [JIRA] (ASTERISK-20750) res_timing_kqueue makes Asterisk use 100% CPU

Rusty Newton (JIRA) noreply at issues.asterisk.org
Mon Dec 3 20:34:45 CST 2012


    [ https://issues.asterisk.org/jira/browse/ASTERISK-20750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200363#comment-200363 ] 

Rusty Newton commented on ASTERISK-20750:
-----------------------------------------

[Valgrind|https://wiki.asterisk.org/wiki/display/AST/Valgrind] with the callgrind option can dump out a profiling report, which could be useful to anyone looking into this issue. You may also want to consider posting any further information including dialplan (extensions.conf) in use, asterisk modules in use, any configuration changes made to Asterisk. Be sure to attach the config files and do not paste them in-line.
                
> res_timing_kqueue makes Asterisk use 100%  CPU
> ----------------------------------------------
>
>                 Key: ASTERISK-20750
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20750
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_timing_kqueue
>    Affects Versions: 11.0.1
>         Environment: FreeBSD 9.0 Release (clean install just to report this bug)
>            Reporter: Oleg Baranov
>
> Asterisk works but one cpu core gets loaded 100%.
> Seems easy to reproduce:
> - Download and unpack Asterisk
> - ./configure  (trivial, with no extra parameters)
> - Enable kqueue in menuselect as mentioned in workaround ASTERISK-20749
> - make ; make install; make samples
> - run asterisk (no config file change required) and monitor cpu load
> timing test produces strange results:
> {quote}
> bsd-cli*CLI> timing test
> Attempting to test a timer with 50 ticks per second.
> Using the 'kqueue' timing module for this test.
> It has been 1000 milliseconds, and we got 413145 timer ticks
> bsd-cli*CLI> 
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list