A joke namespace (Acme) and mixing forks , signals, and threads .... the words "bottomless tarpit quicksand" spring to mind, but I'm not an expert :)

The advice on asking questions still applies, start by writing a minimal self-contained program that reproduces your unwanted behaviour

Good luck

U mean to say that using Acme with the other modules is the cause?

I don't think that's what AM meant... but the mish-mash you cite might do most anything with the possible exception of teaching pigs to fly.

From the Acme::Damn documentation:

"Acme::Damn provides a single routine, damn(), which takes a blessed reference (a Perl object), and unblesses it, to return the original reference. I can't think of any reason why you might want to do this, but just because it's of no use doesn't mean that you shouldn't be able to do it."

It's a really good practice read the docs for all your modules. Reading the rest of those is left as an exercise to tish15. And as AM mentioned, it's really hard to help solve a problem like this (to say nothing of 'hard to find any inventive to do so') without seeing your problem code.

Before posting code though, and before jumping to more unfounded conclusions, please see On asking for help and How do I post a question effectively?.

I fugured out the problem area... My parent thread, after forking child threads is running in while(1) loop... I have done this because at times I need to send signal to the parent thread and hence need the parent thread to continue to exist...

Is there anyway to make the parent thread dormant but continue to exist

It's the loop on line 271.