Welcome to Omgili,
Omgili ( Oh My God I Love It ;) is a search engine for discussions. With Omgili you can find answers and solutions, debates, discussions, personal experiences, opinions and more... To learn more about Omgili click here.
This is a complete preview of the discussion as it was indexed by Omgili crawlers. Use this preview if the original discussion is unavailable.
Click here to view the original discussion.
 |
|
 |
|
phpFreeChat - Web2.0 AJAX chat server - Forum / IE hangs when closing the chat session..
Greetings,
IE hangs when closing the chat session and consumes 100% CPU time..
It is only possible to close IE via task manager
Please provide any hints to investigate..
Cheers, Kishore.
|
|
 |
|
 |
|
|
|
|
1. Do you ever experience this from any other web pages?
2.
Are you able to reproduce the bug on the offical demo?
|
|
|
|
|
|
|
|
|
1) The same is not experienced in other web pages..
2) Will not be feasible to reproduce on the official demo page...
25~ users with varying posts at varying times
-->
Please let me know what happens when the "disconnect" option is pressed or the IE window is closed
Can I enable any logging from this point of time to log the activities + time taken..
|
|
|
|
|
|
|
|
|
I'm not sure what you mean by the second point.
I'm wondering if you are able to reproduce the issue for yourself on the official demo.
I'm not sure what you're talking about when you say "25~ users with varying posts at varying times."
As far as the disconnect/window closed, they aren't the same.
On a disconnect, a message is sent to the server telling it the user left, they are instantly removed from the chat.
However, on a window close, the user only is removed after the timeout period is reached.
This is the only way to reliably track that a user has left.
What sort of logging do you mean...
The chat can be logged, yes.
Or are you wanting to know if the commands sent to and from the server can be logged?
As for those, there's not a built in function, but I imagine you could create one.
I'm not sure it would help solve your issue though.
|
|
|
|
|
|
|
|
|
By the second point..
I mean many users are just logged on and watching..
And only some are posting at different times...
Please clarify "However, on a window close, the user only is removed after the timeout period is reached.
This is the only way to reliably track that a user has left" What is the difference between the disconnect and /quit ?
The "timeout" is set to 10 hours..
Could the system be in some infinite loop because of this setting ?
|
|
|
|
|
|
|
|
|
Ok, let's back up again.
I don't want you to get a bunch of users to all use the official demo.
What I'm asking is if you can make the problem you are having happen on the official demo.
Does the same issue occur on the official demo as with your personal chat?
I already explained disconnecting versus closing the chat.
Disconnect (clicking the disconnect button) ends your session with the chat immediately.
Closing the chat, by closing your browser, leaves your session on until you time out.
A timeout of 10 hours is excessively long.
Time out shouldn't be more that a few minutes tops.
I can't think of any reason why you would want the time out to be that long.
|
|
|
|
|
|
|
|
|
Mmm... I must have misunderstood timeout "This is the time of inactivity to wait before considering a user is disconnected (in milliseconds).
A user is inactive only if s/he closed his/her chat window.
A user with an open chat window is not inactive because s/he sends each refresh_delay an HTTP request.
(Default value: 35000 it means 35000 ms or 35 seconds)"
A user might be inactive for a few hours and I set it to 10 hours..
I do not want the session to be disconnected after a few minutes of inactivity !
|
|
|
|
|
|
|
|
|
You need to reread the explanation...
"A user is inactive only if s/he closed his/her chat window ."
So your users will only be considered inactive when the chat window is closed, otherwise without them doing anything, the window still sends a refresh command to the server, keeping their session open.
As long as they have it up, they wont be inactive.
You definitely need to reduce the timeout to something much much smaller.
|
|
|
|
|
|
|
|