Yes, this is a big problem as it sometimes eats up a lot of CPU resources:
Normally my HE has a load of 1 to 2% (devices and apps). But when such a CC device driver runs amok, everything is possible; I've even seen loads of more than 100%!?! 
BTW, my highscore yesterday:
method runQ of child device ccBüro ran for 752,592ms
=> Over 12 minutes!?! 
It would be very useful to simple have a much lower timeout for such events (configurable, or IMHO a maximum of 10 seconds).
A (non) reaction after 12 minutes is (for me) completely useless. 
