As implied in the CB, no matter how good you think your "recovery processes" may be in the production environment, I think it verges on idiocy errrr hiding your head in the sand to try to suppress what amounts to a warning that there's something seriously wrong.

Other, wiser Monks tried -- again in the CB -- to give you an approach with (IMHO) more merit. For example:

Corion 2006-12-06 11:06:39-05 I'd avoid Win32::Process and use system("start $that_process");. Of course you then lose control over the launched process.

tye offered another; and I may have missed a few folk who shared wisdom. I may also be missing the point/validity of your concern that the popups may go unanswered. My recommendation would be to monitor the production environment until I you found out what's borked.

So, please, tell us WHY you're not more interested in WHY Perl is crashing. Perhaps that info will help us respond more usefully (or (?) acceptably (?)

¹Title changed -- new title lifted from a later remark-of-great-wisdom,-insight-and-frustration in the CB.