On Jun 7, 2006, at 10:42 PM, Bryce Harrington wrote:

Jon was looking into [1501156] last I heard. I've

This is sort of a "cross your legs, blink three times, and sneeze" type

of bug - it is definitely recreatable and should be fixed, but the steps

to trigger it are odd enough that I suspect most people won't encounter

it. In fact, I'd wager that it's been in there for quite a while with

no one noticing it.

Well...

Actually that was to get things to crash. To get a warning assertion to come up there was a lot less to it. And it was one of those warnings that indicated an internal corruption. Let them go and then later on you'll get strange, hard to reproduce side-effects. The crash steps == odd. The initial corruption == much easier to see.

So the lesson here, boys and girls? Don't ignore warnings. They are there for a reason, and you'll have much strange pain and suffering if you ignore them. Much easier to just fix problems at their root.

Oh, and bug 1501156 is fixed.