<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>I experienced the error again today, and this time I was careful to note, the user experience is that the server goes away. Poof, gone. There’s no 500 error or anything; it’s as if the server was never there. I restarted the Dancer process, clicked refresh on web browser, and continued normally. I retried the same sequence of user actions that led to the error, but could not replicate.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Given the intermittency, and that the error appears to surface on any route, I’m starting to wonder if this is some sort of race condition within the <i>before</i> hook of the app? We do some pretty fancy stuff with the <i>before</i> hook to implement a certain feature of the app; maybe I should post some of that code?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In any event, thanks for the continuing discussion. At the risk of encouraging bad habits, Chad, thanks for choosing this issue to procrastinate <span style='font-family:"Segoe UI Emoji",sans-serif'>😊</span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:andy@andybev.com">Andrew Beverley</a><br><b>Sent: </b>Thursday, March 14, 2019 11:56 AM<br><b>To: </b><a href="mailto:dancer-users@dancer.pm">Perl Dancer users mailing list</a><br><b>Subject: </b>Re: [dancer-users] Dancer crashing</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On Thu, 14 Mar 2019 11:47:31 -0700 Chad Wallace wrote:</p><p class=MsoNormal>> > I don't know how else you would get the following fatal error, unless</p><p class=MsoNormal>> > something is actually dying with the message "Use of uninitialized</p><p class=MsoNormal>> > value in subroutine entry"</p><p class=MsoNormal>> > </p><p class=MsoNormal>> > Use of uninitialized value in subroutine entry at</p><p class=MsoNormal>> > /home/hermann/perl5/perlbrew/perls/perl-5.26.2/lib/site_perl/5.26.2/HTTP/Server/Simple.pm</p><p class=MsoNormal>> > line 397.</p><p class=MsoNormal>> </p><p class=MsoNormal>> That one's not fatal, but the one after it is. It's a croak from</p><p class=MsoNormal>> within Socket's XS code.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Ah, I see what you mean. I didn't scroll down enough :)</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Andy</p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>dancer-users mailing list</p><p class=MsoNormal>dancer-users@dancer.pm</p><p class=MsoNormal>http://lists.preshweb.co.uk/mailman/listinfo/dancer-users</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>