We ran into this in out application the other day, and it's a surprisingly "normal" thing to do to result in a hard crash of a browser. I'm especially curious

We ran into this in out application the other day, and it's a surprisingly "normal" thing to do to result in a hard crash of a browser. I'm especially curious if anyone knows: 1. Is there any hope of this being fixed in the near-term? The MS bug report didn't have much information. I'd sure like to avoid implementing the somewhat crazy workaround if I can help it. 2. It seems like this ought to be a pretty widespread problem. Are others seeing it? Are there other workarounds that aren't so ugly?