Comment 7 for bug 145282

I did actually add a check for verbose mode yesterday, so that the log message's size and content are not calculated unless it'll be used, and hence g_list_length won't be called. This closes the presenting problem. But we still have the difficulty that the presenting problem can only have been caused by a degenerate list, which would have caused problems further down the line, and the real problem would have been finding where this list went bad. However, we can't do that unless we can replicate, and we've only had one report of this problem. Hence, I'm closing this upstream as INVALID. However, if this happens again, let us know.