Are the previous comments hinting at the story?
# This is the select loop itself. We do a Bad Thing here by polling
# for socket activity, but it's necessary with ActiveState's Tk.
#
# -><- We should really stop the poller when there are no handles to
# watch and resume it as needed.
Any solutions come to mind?
-Craig
On May 2, 2007, at 7:45 PM, David Davis wrote:
POE::Loop::TkActiveState is using select with a timeout of 0. That
doesn't
look right to me.
my $hits = select(
my $rout = $loop_vectors[MODE_RD],
my $wout = $loop_vectors[MODE_WR],
my $eout = $loop_vectors[MODE_EX],
0,
);
David
On 5/2/07, John R. <[EMAIL PROTECTED]> wrote:
John R. wrote:
> I just joined the mailing list...sorry about then new thread...
>
> I am experiencing the same problem: single CPU / 100%
utilization when
> idle.
>
> POE: 0.99.89
> Tk: 804.027
> Perl: v5.8.8 built for i686-linux
>
> John
>
strace snippet:
gettimeofday({1178152425, 688201}, NULL) = 0
gettimeofday({1178152425, 688279}, NULL) = 0
select(5, [4], [], [], {0, 0}) = 0 (Timeout)
gettimeofday({1178152425, 688355}, NULL) = 0
gettimeofday({1178152425, 688387}, NULL) = 0
select(5, [4], [], [], {0, 0}) = 0 (Timeout)
That pretty much is in a loop.
John
