summary... it was broken during development of 1.6, it's not needed in 1.7 (use async loading instead) and it doesn't seem there were any objections to not fixing it in 1.6. i personally have no need for debugAtAllCosts but i'm surprised there was no reaction to the post linked to above.