TextToTalk crash Dalamud due to an unhandled SSML parsing exception.

[Waitsnake]

Environment:

• Windows 11
• Dalamud 14.0.0.3
• TextToTalk 1.35.3.0 (testing)
• System backend (System.Speech)

Error excerpt:
System.FormatException: XML content not valid.
System.Xml.XmlException: Name cannot begin with the '3' character
at System.Speech.Internal.Synthesis.SsmlParser.Parse(...)
at TextToTalk.Backends.System.SystemSoundQueue.ASyncSpeak(...)

This occurs during normal playback (e.g. player chat), without TextAdvance or manual cancellation.
It appears that invalid SSML generated from runtime text is passed to System.Speech without validation or exception handling.

Result:
Unhandled exception on a worker thread causes a CLR crash and terminates Dalamud/FFXIV.

Expected:
Invalid SSML should be caught and ignored, sanitized, or fall back to plain text instead of crashing the host.

Dalamud crash log:

dalamud_appcrash_20260103_174753_645_3264.log

[Waitsnake]

Just to clarify my understanding of commit ea9b31a:
does this mean that receiving a <3 (the very often used heart emote) in chat could crash the game when using the system backend, due to invalid SSML?

I’ve been using the websocket backend exclusively for the past few days because repeated crashes made me hesitant to use the system backend at all.