Yes, my apologies. I should provide you a more comprehensive log. I am working on pinpoint the line that triggers this message. It behaves almost like a segfault, but I'll do my best to locate the error prone line. Sorry for the incomplete picture -- I'll post an update today.