>Here is what I found:
>
>Chrome has a bug when working with frames. A hit on the dashboard frame will be resend to the server if another hit is done on another frame. This is related to something close to that. So, if you do a Time warp and then you do a refresh, which is a hit in another frame, this will fire back the last hit on the other frame. But, it sends it without any variables. It is still a POST. So, that had a severe impact on the site. Because, this is something I never expected. So, basically, it was trying to retrieve a large chunk of messages, which doesn't make any sense. So, if I detect that a Time warp hit is sent without any variable, I will simply return a blank page and that will avoid the rest of the code to be executed thus avoiding the large chunk of messages to be selected. So, basically, in such a sequence, the first hit for a refresh will give you the new messages, and because Chrome will fire back another transaction, I have no choice but to return a blank page.
>
>I do not know when they will release a fix. But, the problem is that this overwrites the messages you just got in your refresh.

Hi Michel,

There has been a recent upgrade for Chrome - a few days ago. With the workaround you installed, it is hard for me to tell whether this particular problem was solved.