Bug #76970 for POE-Loop-EV: bug at Kernel.pm line 1013

Thu May 03 15:53:24 2012 chinalw81 [...] gmail.com - Ticket created

Subject:	bug at Kernel.pm line 1013
Date:	Fri, 4 May 2012 03:53:12 +0800
To:	bug-poe [...] rt.cpan.org
From:	melchior Liao <chinalw81 [...] gmail.com>

please report this stacktrace to bug-poe@rt.cpan.org at /usr/local/share/perl5/POE/Kernel.pm line 1013. POE::Kernel::_dispatch_event('POE::Kernel=ARRAY(0x19273b8)', undef, 'POE::Kernel=ARRAY(0x19273b8)', '_stop', 8, 'ARRAY(0x21537c0)', '/usr/local/share/perl5/POE/Resource/Sessions.pm', 571, undef, ...) called at /usr/local/share/perl5/POE/Resource/Sessions.pm line 568 POE::Kernel::_data_ses_stop('POE::Kernel=ARRAY(0x19273b8)', 'POE::Session=ARRAY(0x16a0ed8)') called at /usr/local/share/perl5/POE/Resource/Sessions.pm line 392 POE::Kernel::_data_ses_gc_sweep('POE::Kernel=ARRAY(0x19273b8)') called at /usr/local/share/perl5/POE/Resource/Events.pm line 325 POE::Kernel::_data_ev_dispatch_due('POE::Kernel=ARRAY(0x19273b8)') called at /usr/local/share/perl5/POE/Loop/EV.pm line 76 POE::Kernel::_loop_timer_callback('EV::Periodic=SCALAR(0x17a5e08)', 512) called at /usr/local/share/perl5/POE/Loop/EV.pm line 111 eval {...} called at /usr/local/share/perl5/POE/Loop/EV.pm line 111 POE::Kernel::loop_run('POE::Kernel=ARRAY(0x19273b8)') called at /usr/local/share/perl5/POE/Kernel.pm line 1235 POE::Kernel::run('POE::Kernel') called at mycode.pl; ============================================================== uname -a Linux my-pc 2.6.32-131.0.15.el6.x86_64 #1 SMP Sat May 21 10:27:57 CDT 2011 x86_64 x86_64 x86_64 GNU/Linux

Sun May 06 00:36:06 2012 RCAPUTO [...] cpan.org - Correspondence added

On Thu May 03 15:53:24 2012, chinalw81@gmail.com wrote: Show quoted text

> please report this stacktrace to bug-poe@rt.cpan.org at > /usr/local/share/perl5/POE/Kernel.pm line 1013.

[....] Thank you for the bug report and backtrace. It looks like POE::Loop::EV may be involved. Can you verify whether the program still crashes without using POE::Loop::EV? This will either confirm or rule out POE::Loop::EV as the problem's cause. That will help focus my investigation. Also, is it possible to send a test program I can run to trigger the problem here? This will be a lot easier to debug if I can watch it fail. Thanks again!

Sun May 06 00:36:08 2012 The RT System itself - Status changed from 'new' to 'open'

Tue May 08 11:18:14 2012 chinalw81 [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #76970] bug at Kernel.pm line 1013
Date:	Tue, 8 May 2012 23:18:01 +0800
To:	bug-POE [...] rt.cpan.org
From:	melchior Liao <chinalw81 [...] gmail.com>

Thank you for you reply. my English is poor. this is my Code. POE::Loop::EV is involved. use EV; #use POE::Kernel { loop => 'POE::XS::Loop::EPoll' }; use POE; use HTTP::Request::Common qw( GET ); use POE qw( Component::Client::HTTP ); POE::Component::Client::HTTP->spawn( Alias => "AsynchHTTPClient" ); my $requiringURL = 'http://www.ptxhf.com/thread-54901-1-1.html' ; POE::Session->create( inline_states => { _start => sub { $_[KERNEL]->post( AsynchHTTPClient => request => GETResponseEvent => GET $requiringURL ); }, GETResponseEvent => sub { } } ); POE::Kernel->run(); exit(0); The code will be fine when i using POE::XS::Loop::EPoll, Thanks ! 2012/5/6 Rocco Caputo via RT <bug-POE@rt.cpan.org>: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=76970 > > > On Thu May 03 15:53:24 2012, chinalw81@gmail.com wrote:

>> please report this stacktrace to bug-poe@rt.cpan.org at >> /usr/local/share/perl5/POE/Kernel.pm line 1013.

> [....] > > Thank you for the bug report and backtrace. > > It looks like POE::Loop::EV may be involved. Can you verify whether the program still crashes > without using POE::Loop::EV? This will either confirm or rule out POE::Loop::EV as the problem's > cause. That will help focus my investigation. > > Also, is it possible to send a test program I can run to trigger the problem here? This will be a > lot easier to debug if I can watch it fail. > > Thanks again!

Sat May 12 15:03:10 2012 RCAPUTO [...] cpan.org - Queue changed from POE to POE-Loop-EV

Sat May 12 15:04:42 2012 RCAPUTO [...] cpan.org - Correspondence added

I couldn't get POE::Loop::EV to pass tests here, so I'm assuming it's a problem with that module. I've put this ticket into POE::Loop::EV's bug queue. Hello, Andy! On Tue May 08 11:18:14 2012, chinalw81@gmail.com wrote: Show quoted text

> Thank you for you reply. > my English is poor. > > this is my Code. POE::Loop::EV is involved. > > use EV; > #use POE::Kernel { loop => 'POE::XS::Loop::EPoll' }; > use POE; > use HTTP::Request::Common qw( GET ); > use POE qw( Component::Client::HTTP ); > > > > POE::Component::Client::HTTP->spawn( Alias => "AsynchHTTPClient" ); > > my $requiringURL = 'http://www.ptxhf.com/thread-54901-1-1.html' ; > > POE::Session->create( > inline_states => { > _start => sub { > > > $_[KERNEL]->post( AsynchHTTPClient => request => > GETResponseEvent => GET $requiringURL ); > }, > > GETResponseEvent => sub { > > } > } > ); > > > POE::Kernel->run(); > > exit(0); > > The code will be fine when i using POE::XS::Loop::EPoll, > > Thanks ! > > 2012/5/6 Rocco Caputo via RT <bug-POE@rt.cpan.org>:

> > <URL: https://rt.cpan.org/Ticket/Display.html?id=76970 > > > > > On Thu May 03 15:53:24 2012, chinalw81@gmail.com wrote:

> >> please report this stacktrace to bug-poe@rt.cpan.org at > >> /usr/local/share/perl5/POE/Kernel.pm line 1013.

> > [....] > > > > Thank you for the bug report and backtrace. > > > > It looks like POE::Loop::EV may be involved. Can you verify whether

> the program still crashes

> > without using POE::Loop::EV? This will either confirm or rule out

> POE::Loop::EV as the problem's

> > cause. That will help focus my investigation. > > > > Also, is it possible to send a test program I can run to trigger the

> problem here? This will be a

> > lot easier to debug if I can watch it fail. > > > > Thanks again!

Fri Jan 16 14:24:18 2015 DBOOK [...] cpan.org - Correspondence added

Provided code runs successfully here under 0.10. Closing.

Fri Jan 16 14:24:30 2015 DBOOK [...] cpan.org - Status changed from 'open' to 'resolved'

Fri Jan 16 14:24:30 2015 DBOOK [...] cpan.org - Fixed in 0.10 added