This is on Empathy 3.10.2 using Telepathy Haze/Logger 0.8.0.

A contact of mine sends messages from a (likely misconfigured or broken) client which occasionally includes literal (terminal?) escape-sequences within messages. If certain escape-sequences are written to the Telepathy logs, double-clicking his contact within Empathy will henceforth fail to open the chat window.

When running empathy-debugger, trying to open the chat window in such circumstances will segfault the debugger. Before segfaulting, the debugger will issue the following warnings:
> (empathy-debugger:4171): Gtk-CRITICAL **: gtk_list_store_get_value: assertion 'iter_is_valid (iter, list_store)' failed
> (empathy-debugger:4171): GLib-GObject-WARNING **: gtype.c:4215: type id '0' is invalid
> (empathy-debugger:4171): GLib-GObject-WARNING **: can't peek value table for type '<invalid>' which is not currently referenced
Segmentation fault (core dumped)

The minimal subset of the log which triggers this bug is the following:

<?xml version='1.0' encoding='utf-8'?>
<?xml-stylesheet type="text/xsl" href="log-store-xml.xsl"?>
<log>
<message time='20131226T21:00:26' id='XXX' name='XXX' token='' isuser='false' type='normal'>&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~&#x1b;[6~valid message follows here</message>
</log>