Skip Menu |

This queue is for tickets about the POE-Component-Client-Keepalive CPAN distribution.

Report information
The Basics
Id: 38263
Status: rejected
Priority: 0/
Queue: POE-Component-Client-Keepalive

People
Owner: Nobody in particular
Requestors: melazyboy [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



file the bug http://rt.cpan.org/Public/Bug/Display.html?id=38262 too not sure if (in cleanup) Can't call method "free" on an undefined value at C:/strawberry/perl/site/lib/POE/Component/Connection/Keepalive.pm line 44 during global destruction. Sessions were started, but POE::Kernel's run() method was never called to execute them. This usually happens because an error occurred before POE::Kernel->run() could be called. Please fix any errors above this notice, and be sure that POE::Kernel->run() is called.
You reported the following error: (in cleanup) Can't call method "free" on an undefined value at C:/strawberry/perl/site/lib/POE/Component/Connection/Keepalive.pm line 44 during global destruction. Sessions were started, but POE::Kernel's run() method was never called to execute them. This usually happens because an error occurred before POE::Kernel->run() could be called. Please fix any errors above this notice, and be sure that POE::Kernel->run() is called. "(in cleanup)" and "during global destruction" in the first message indicates that objects within POE::Component::Client::Keepalive are being destroyed (and thus deallocating resources) while your program is exiting. This is an abnormal condition since PoCo::Client::Keepalive's resources normally keep a program running. The second message, which includes "This usually happens because an error occurred before POE::Kernel->run() could be called." indicates that your program probably crashed before POE::Component::Client::Keepalive could fully initialize. This would explain why cleanup failed---the component was left in an inconsistent state due to an error, most likely in your code. Unfortunately no test case was included in the bug report, so I'm unable to reproduce the issue. Since we're at an impasse, I am rejecting the ticket. Please feel free to reopen the ticket with a test case or a more actionable description of the situation leading up to the crash. Thank you.