Comment 30 for bug 345714

Hi Robbie,

Okay sounds good. Meanwhile, I sussed out 348428. I believe it is attributable to a fix I'd put in for bug 344740, which I was a bit uncertain about at the time, although the patches looked innocuous enough; but looks like my gut was right. I've backed out one of the two patches I suspect may be the culprit. Please re-test to verify this fixed the issue; if not I will back out the other patch too. Hopefully that puts this bug to rest.