I'm running the "Developer" edition of WSJTx rc4 which is what might be called an "Alpha" version.  

I was decoding TT8XX on 17m in Hound mode with 3 streams and then this happened.  (See attached)

I was not really watching WSJTx and turned away to do something else when my Enable Tx was activated after it had timed out and was in standby.  And I was excited about a potential new band counter.  But there were a couple of clues that I completely overlooked, the bogus V34 call and the +14 from CHAD.  I only run 100w on my Mosley at 35'.  

Then Keith (K5YCM), JTA texted me that I was calling on EVEN.  I was still in "H" and the "Tx even" was unchecked and grayed out, but there I was spamming the frequency.  I stopped and scrolled back and found this.  Had I been paying closer attention, I "might" have caught the bogus call on the left and the "?" and such to the right and halted the transmission, but I didn't.  Plus, I never realized that I was seeing all the odd decodes showing up in the BA window.  Too much BIC screen time.  At least I just looked like a certified LID and not some out of band operation.  OK Joel, what's the award for this activity?  

BTW, I do like the inability to double click on a compound call on the main watering holes in the latest version.  Maybe that will keep the P5's from showing up on them causing mass confusion.  At least the true station's call will have to be manually entered now.  This is not in effect when NOT on the main frequencies.   I'll give that a try next time I see the situation, even though I typically avoid the stations that do that as it only encourages bad behavior on their part.