I appreciate you guys looking into this so quickly, but let's dig a little deeper.

1. STINNER Victor, you claim this is already fixed in 3.4 by the link, however this doesn't really help since I'm not even up to 3.3 yet (though I'm considering it, I meant to select 3.2 above).  No one has yet provided any insight into why this condition only occurs when firefox is up running shockwave flash...(to me this is an even bigger question as I have a 7 other rather under tasked cores at my disposal).

2.  Mark Dickinson, let's break this down.  I've already worked around it as I’m sure that EVERYONE ELSE WHO USES IT has already done as well...  We know as coders it's more difficult to work with a varying format (no advantage there).  Which begs the question why not fix it so everyone doesn't have to?  By the issue you referenced it's been known and unfixed since at least since 2004.  Also, no curiosity why this only occurs when running firefox w/shockwave flash?

Again I do appreciate you guys looking into this so quickly, but I don't know if this is actually going to get fixed, why it wasn't fixed in 2004, or is the Python motto "it's not broke if there exists a workaround".  Odd that more time was spent talking about this (and Mark and myself independently implemented actual fixes) than the fix would have taken to apply to the baseline(I used to see this much other places I've worked).  But I'm happy to say, I never saw responses back so quickly, which is very hopeful.

Sincerely,
Dave