First: my responses to this thread should be viewed as official announcements / responses. I am the person responsible for this bug. You're not going to get anyone on the team who a ) knows more about the bug or b ) knows more about our progress with it, than me.
To the folks asking for a broad announcement, that's unlikely. In general we communicate about bugs that were raised in this forum, using this forum. Post your info in this thread, and watch for my responses. PM or email me if you feel I haven't communicated in a long time. It may not be obvious, but our workload is incredibly heavy, and I may forget to pop in here and check in, unless I have something new to say.
I am working on this bug and will communicate when I make progress. Thanks to all of the folks who have provided me turns and other assistance. Unfortunately, this is a bug with no obvious source and has so far proven incredibly difficult to fix.