TeamSpeak 3 suffered from an issue demonstrated here: http://r4p3.net/public/ts3bbcgenerator/
I believe Mumble fixed this in version 1.2.6 or 1.2.5. Is anyone able to inform me of when this was fixed? I would appreciate it! I would like to know for research purposes. I'm trying to compare TeamSpeak against Mumble, me being in favor of Mumble.
Looks like this is the issue you're talking about: https://github.com/mumble-voip/mumble/issues/1251
Wow, that is EXACTLY the issue. Thank you very much Pilot_51 much respect your way. This was specifically a TeamSpeak 3 targeted attack and Mumble fixed it before TeamSpeak developers did. A perfect example of open source kick ^&$! (I briefly tested it on Mumble once by translating the BB Code to HTML and to surprise it did work on Mumble. This is strictly an issue with the QT framework image source handling and Windows I believe.) It has something to do with mapped network drives or calling a Windows domain as seen here by looking for "//": http://goo.gl/cGE0Uj
I'm interested in more of a REAL computer science explanation as to why this triggered a freeze on Windows, but not UNIX systems.