Comment 2 for bug 302698

for the mostly-there case, I think its a damaged-by-previous-code case; it needs repair as all such cases do.

For the new push, I think there is a different problem - a backtrace would be good.