Although this topic is now marked as resolved, I'd like to take the opportunity to remind the attentive reader.

It is generally not considered acceptable for well-behaving programs to crumple under load with symptoms of memory corruption. Indeed, grabbing resources in an endless loop can serve as a useful stress-test for validating the robustness of your utility.

One common cause of such errors is not testing the return value of malloc()/realloc(), and blindly assuming they always succeed. See also: canthappen.pdf.