Descriptive Problem Summary:
I woke up this morning to see this in my pager:
Failed to decompress message of length 99558 (zipped 77903)
BYOND(454.1036) Debug: failed to unzip message 67,77909.
EDIT: here's some more, from the night of october 14th to october 15th.
Failed to decompress message of length 93653 (zipped 72808)
BYOND(454.1036) Debug: failed to unzip message 67,72814.
Failed to decompress message of length 31984 (zipped 28489)
BYOND(454.1036) Debug: failed to unzip message 67,28495.
Failed to decompress message of length 52294 (zipped 43443)
BYOND(454.1036) Debug: failed to unzip message 67,43449.
Failed to decompress message of length 53591 (zipped 43905)
BYOND(454.1036) Debug: failed to unzip message 67,43911.
Failed to decompress message of length 61590 (zipped 51245)
BYOND(454.1036) Debug: failed to unzip message 67,51251.
END EDIT.
SECOND EDIT
Failed to decompress message of length 110470 (zipped 84564)
BYOND(460.1052) Debug: failed to unzip message 67,84570.
This is from sometime between December 11th to December 12. I'm behind a wireless router right now. When this bug entry was posted, I was using a wired router. Might be helpful, might not. Using 460.1052 this time.
END SECOND EDIT
THIRD EDIT
This is from the early morning of october 30th 2009.
Failed to decompress message of length 150195 (zipped 118172)
BYOND(461.1054) Debug: failed to unzip message 67,118178.
Failed to decompress message of length 187208 (zipped 138062)
BYOND(461.1054) Debug: failed to unzip message 67,138068.
END THIRD EDIT
Numbered Steps to Reproduce Problem:
Unknown.
Does the problem occur:
Every time? Or how often?
This is the first time in many byond updates.
In other games?
Not a game issue, that I can see.
In other user accounts?
I have not looked into it.
On other computers?
I have not looked into it.
When does the problem NOT occur?
Unknown.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked?
I reported this issue a long time ago (maybe over a year?) and got my name into the release notes for it. Since then, it hasn't happened again until now. It used to happen hourly back then.
Workarounds:
Unknown.
ID:83699
![]() Oct 12 2009, 6:54 am (Edited on Dec 30 2009, 11:04 am)
|
|||||||||||
| |||||||||||
If I had to guess, I'd think someone tried paging you when it was "froze", and it failed to receive the message properly.