I've seen this randomly happen since 2.4.
Slouken once said its some kind of desync issue in the client/server protocol, and since its random it would be very hard to fix.
It very rarely happens to me, maybe once in 2 weeks, so nothing to make a big fuss about.
Are you sure it was Slouken who said that? Because I had it happen to me very shortly after 2.4 (afaik I was probably one of the first to experience it and mention it) and was talking to Zootfizzle on IRC while it was still effecting my character and he said it had to be some kind of client/server desync caused by a race condition and would be extremely hard to hunt down.
Are you sure it was Slouken who said that? Because I had it happen to me very shortly after 2.4 (afaik I was probably one of the first to experience it and mention it) and was talking to Zootfizzle on IRC while it was still effecting my character and he said it had to be some kind of client/server desync caused by a race condition and would be extremely hard to hunt down.
I don't think it's a desync issue. Keep in mind these are all user reports, so while I think they are accurate it's nothing I've confirmed myself: It looks to be some sort of overflow error. People who have had it break can clear the combat log and it'll immediately start working, without a relog or a reload like you normally do to fix it.
The info got sent off to Blizzard, so hopefully it helps them fix it.
It looks to be some sort of overflow error. People who have had it break can clear the combat log and it'll immediately start working, without a relog or a reload like you normally do to fix it.
Is this some internal storage which is always filled by all (unfiltered) events or only the storage for the filtered combat log entries?
So would the problem also be fixed if all events are filtered out in the Blizzard combat log settings?
It's not really an easy thing to test or duplicate, personally I get the error once every 6 months and as it's a persistent error it's hard to do some real checking. I'm pretty sure I've had it even when the filtered combat log is disabled, but I'm not positive.
I only had this issue in 'Trial of the (Grand) Crusader' 3 or 4 times so far, never in an other instance and never in the normal world...but it looks like it can happen anywhere, anyway:
Playing without Combat Log is really wonderful. It's a skill test for all Addon junkies. :)
Is anybody else having issues with all chat windows resetting their positions when swapping between characters? Even with no addons loaded they all move around.
It's driving me nuts having to reposition this crap 5+ times a day.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
http://wowinterface.com/downloads/info16001-CombatLogFix.html
http://github.com/Shadowed/CombatLogFix
Are you sure it was Slouken who said that? Because I had it happen to me very shortly after 2.4 (afaik I was probably one of the first to experience it and mention it) and was talking to Zootfizzle on IRC while it was still effecting my character and he said it had to be some kind of client/server desync caused by a race condition and would be extremely hard to hunt down.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI don't think it's a desync issue. Keep in mind these are all user reports, so while I think they are accurate it's nothing I've confirmed myself: It looks to be some sort of overflow error. People who have had it break can clear the combat log and it'll immediately start working, without a relog or a reload like you normally do to fix it.
The info got sent off to Blizzard, so hopefully it helps them fix it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIs this some internal storage which is always filled by all (unfiltered) events or only the storage for the filtered combat log entries?
So would the problem also be fixed if all events are filtered out in the Blizzard combat log settings?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt's not really an easy thing to test or duplicate, personally I get the error once every 6 months and as it's a persistent error it's hard to do some real checking. I'm pretty sure I've had it even when the filtered combat log is disabled, but I'm not positive.
Playing without Combat Log is really wonderful. It's a skill test for all Addon junkies. :)
It's driving me nuts having to reposition this crap 5+ times a day.