Welcome to the Forum Archive!

Years of conversation fill a ton of digital pages, and we've kept all of it accessible to browse or copy over. Whether you're looking for reveal articles for older champions, or the first time that Rammus rolled into an "OK" thread, or anything in between, you can find it here. When you're finished, check out the boards to join in the latest League of Legends discussions.

GO TO BOARDS


Spamming Errors.

Comment below rating threshold, click here to show it.

Hahajama

Junior Member

04-26-2011

i got this too. a few people in my game probably experienced the same thing just before it happened to me because they left too


Comment below rating threshold, click here to show it.

GG Dirgimzib

Member

04-26-2011

Yeah, I'm PRETTY sure an error has occurred here. Not enough to crash my client, but I did notice some lag in game. :S

Not sure on the exact number, but there were close to 100 of these error reports.

And they all say this, just with different correlation and message IDs:
(mx.messaging.messages::ErrorMessage)#0
body = (Object)#1
clientId = (null)
correlationId = "22C767A3-0643-7CBA-EFE3-910352E8F597"
destination = ""
extendedData = (null)
faultCode = "Client.Error.RequestTimeout"
faultDetail = "The request timeout for the sent message was reached without receiving a response from the server."
faultString = "Request timed out"
headers = (Object)#2
messageId = "1709DD44-BC08-A511-498E-91043E503DDF"
rootCause = (null)
timestamp = 0
timeToLive = 0


Comment below rating threshold, click here to show it.

AruBunny

Junior Member

04-26-2011

Uh, bumping. This has still not been addressed by riot for some reason. Many computers were frozen, which is much more serious than an error that only affects the game. Plus, there are a lot of leaves waiting to be erased, apologies to be given, wins to be granted, etc.


Comment below rating threshold, click here to show it.

AruBunny

Junior Member

04-27-2011

Bumping again. Sigh.