|
|
|
[
Permlink
| « Hide
]
Simon Nolan added a comment - 08/May/07 08:34 PM
Closing as duplicate.
I'm reopening this.
The issue this was linked to as a duplicate was a two part issue (an error occuring when sending a Group IM and the IM session reopening). That issue has been closed since the error message has been fixed. However as of 1.17.2, the issue here (Group IMs reopening when someone send an IM after you have left the session) is still occuring, and has been since 1.15 Raising to major - the fact that it is not possible to leave a Group IM session that doesn't interest you, has effectively rendered the chat feature of Groups unusable since 1.15.
Many groups which used to tolerate informal chat, now operate a no chat apart from the Group owners policy - this has had a detrimental affect on the general friendliness and helpfullness of these Groups and SL as a whole. I second Matthew: this bug makes the groups a source of spam and pretty much impossible to use for their intended purpose (communicating between people sharing the same interests as yours), unless you are ready to become a spammer yourself...
Please, fix it soon !!! Can you please supply more details on what you're seeing with this? I've tried with numerous group IMs and I close it and they do not pop back open after several seconds.
This bug is still present in v1.18.3.5, even if in a much lesser measure than in v1.18.2 and previous versions. The chat session will get reopened whenever many IMs are coming in while you close it.
It looks like if the lag in the IMs transmission is the culprit: it's like if the viewer takes into account the time when the IM was emitted and not the one when it arrives, compares it to the time when the session was closed by the user, and reopens the said session (i.e. lets the IM go through) whenever the IM was emitted before the session was closed. I didn't look at the code to verify this hypothesis, but it is what it feels like to me... Also, I have seen IMs coming out of order (i.e. the reply to an IM arriving before the IM it replied to)... which might be related to this bug. As a complement to my last comment, I must say that I only encountered this behaviour in group IMs sessions.
we couldn't reproduce this internally. please reopen if you can provide us with consistently reproducible steps. thanks
> we couldn't reproduce this internally. please reopen if you can provide us with consistently reproducible steps. thanks
This bug happens at random. I found no reliable way to reproduce it... Simply stay logged and close the group IMs windows whenever they open: after a while you will notice this bug. Of course, if you test it from withing LL's local network, you might well never encounter it... Yet, I noticed something. Whenever the bug occurs, I get: WARNING: dispatch: Ignoring unknown message ChatterBoxSessionLeaveReply in the log... You get that message whenever you close a group tab, it's not relevant to this issue.
I can almost guarantee this is a packet latency issue... the messages get "crossed", your "close" request comes in at nearly the same time as a new message. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||