22 replies to this topic

[adin_odmin]

Summary: Posting ">_<" smile into ingame chat crashes all clients connected to the server.
Steps to Reproduce:
1.Connect to any game.
2.Type >_< in chat window (doesn't matter if it would be team chat or general chat).
3.Press Send Button or hit Enter
4.See how your (& other ppl too) game freezes
Frequency: I've tried it 5 times with & without spaces - & got crash 5 times. I have not checked posting ">","<" or "_" without other characters.
I've also found some people who were on the same server with me at the same time & they confirmed that the game crashed for them too (even if >_< was typed only on my side).
UPD: My big ThnX to Volkan & pupp3t, who helped to reproduce this bug.
After explaining how to reproduce the bug someone did crashed my game too

System Specs: (If I'm not rlly sure that it's relevant in such case,but) OS Win7 x64, i5, RAM - 4G, GPU - Nvidia GT 525M

Plz fix this asap as it's kind of showstopper

Edited by adin_odmin, November 27 2012 - 02:52 AM.

[Necro]

wut...must try

>.>

[Astrolis]

bump! if this can be reproduced for others... will check it today. ty for the heads up!

[Astrolis]

JUST CHECK IT! ITS A REAL BUG. seriously wow... was very surprised... DEVS get on it!

Now thats is public anyone can use it to end games that they are losing or just to troll people.

Edited by Astrolis, November 26 2012 - 04:27 PM.

[Necro]

CONFIRMED!!!

Weirdest bug EVAR!!

[Astrolis]

bump

[Spiderz]

devs need to see this asap

[Necro]

It would be funnier if this was a console command a devs put in for trolling.

Also sorry for everyone in that siege game i just crashed

Also we may want to remove the symbols that cause this and instead message the devs to not cause rampant people crashing everyone for the rest of the CB3.

Edited by Necro, November 26 2012 - 04:49 PM.

[MerryAgony]

I've escalated this internally - thanks all who posted!

[Volkan]

also >.<

not just the _

i have a gut feeling it may also be any character inbetween > < but havent tested yet.

[Ollie]

Also, any < or > simply disappears without the other (e.g., <3)

[Spiderz]

personally i'd hide this thread before it gets a tad viral, i don't want rage quitters crashing me instead of disconnecting.

[ArnieF4440]

Lol, I'd a character encoding or special character issue ... bit of a derp. Its why I use generic exception handling throughout my programs XD

try{
//everything!
} catch (Exception e) {
// something went wrong error
}

[Scapes]

Huh. Last event, all it did was muck up the chat interface.

[G4M5T3R]

I hope this is fixed by Open Beta

[Dread_Lord_Pitr]

Guess that explains why i got thrown out of a server last night when i typed >_<

[HellRik]

Rofl

I wish I had seen this post earlier. I'll stop using it. I crashed so many time trying to answer someone in chat between deaths.
LOLZ!

I also crashed upon using a friend invite to join his game couple minutes later while I was already in a game. By crash I mean that the LAUNCH bouton to spawn me back into game was stuck on ''Shync''

Edited by HellRik, November 26 2012 - 07:39 PM.

[JuiceBox]

Scapes, on November 26 2012 - 05:37 PM, said:

Huh. Last event, all it did was muck up the chat interface.

I suggest this thread gets locked AND moved.

I just did >< in chat and bam.. crashed.

[JustJake]

ArnieF4440, on November 26 2012 - 05:23 PM, said:

Lol, I'd a character encoding or special character issue ... bit of a derp. Its why I use generic exception handling throughout my programs XD

try{
//everything!
} catch (Exception e) {
// something went wrong error
}

Pokemon exception handling is a worst practice! It's better to find and stop those exceptions at the source!

[ArnieF4440]

JustJake, on November 26 2012 - 07:41 PM, said:

ArnieF4440, on November 26 2012 - 05:23 PM, said:

Lol, I'd a character encoding or special character issue ... bit of a derp. Its why I use generic exception handling throughout my programs XD

try{
//everything!
} catch (Exception e) {
// something went wrong error
}

Pokemon exception handling is a worst practice! It's better to find and stop those exceptions at the source!

Sometimes you can't avoid it unfortunately. I've had a couple of projects that needed that XD