Yes, it's not because of the user properties, but because of a message I've sent on purpose to check if a bug I'm trying to analyze exists on the stax deployment, too. The message is appropriately called "Boom" :)
For some reason the textile formatter doesn't play well with LiftSession processing. The message in question is eventually formatted in the following fashion: <blockquote><p>Boom</p>\u000a</blockquote>\u000a The \u000a character is the newline character and should be treated as whitespace, so this shouldn't matter, but who knows... Note: if you resend this message, this will also crash the regular timeline... Sorry about this unpleasant surprise, now trying to debug the issue. Vassil
