Re: Certain msgs crashing TOT fire

Believe it or not, the devs have actually hit this bug before, but we 
have been unable to track it down.

It would help greatly if you could tell me the EXACT messages that were 
SENT!  Then I can track this down.  I suspect that it is an xml 
encoding issue.

On Jun 2, 2004, at 1:33 AM, brett wrote:

> Ive run into a way to crash fire today.  Someone sent me these msgs 
> thru MSN - You get notifed that they have sent a msg, but their is no 
> text to their msg that is shown, and the date stamp changes to "NaN:: 
> AM".  After about two of these msgs fire will crash (ive included the 
> crashlog below).  From what i can understand these msgs are supposed 
> to trigger sound effects on the users computer
>
> The following is what shows up in console.log when it happens:
>
> Entity: line 1: parser error : internal error
> <message>@13No2 excuse13!</message>
>          ^
> Entity: line 1: parser error : Extra content at the end of the document
> <message>@13No2 excuse13!</message>
>          ^
>
> And here a few of the other msgs that casue the problem aswell
> <message>   %13XxxxXxxxX</message>
> <message>&quot;4Mua5ha4ha5ha4ha5!</message>
> <message>L6Right...</message>


------------------------------------------------------------------
Graham Booker                   Texas A&M University
[email protected]    Graduate Student in ELEN
------------------------------------------------------------------