I can't say if it is the case here but any time that I've encountered Carp::Heavy errors/warnings it has been a problem not with Carp::Heavy but with the parent program consuming too many system resources such as memory or open file handles.

Update: Looks like it was a Carp::Heavy problem this time. See Steve_p's answer below.

--
John.