well I find this quite annoying.

I logged in and after being in for oh...30 seconds, without any warning whatsoever, all my screens just shut down. So I was logged out of the game server AND the normal browsing page also closed.

This was the first time it happened on this computer but yesterday; I was showing a friend how funkypool works on his laptop and the same thing happened three times.

We both have laptops...and this has never happened before. Now I try to log back in and it says that I cant because my browser wont let me and to wait a few minutes.

whats going on and how can I stop it??

When Internet Explorer dies, all the pages that opened "from" that page also die: they belong to the same process. So when you click a link and it opens in a new window, and one of those pages dies, the other dies too. So if your game window died, that'll take the main page with it too.

Presumably then, due to the way that the game window ended suddenly, as far as any pertinent processes are concerned (or at least ones that seek to prevent multiple game windows being open), your game is still active and you can't log in again, presumably for 20 minutes, after which you'd have been logged out anyway if you were inactive.

As for the cause of this problem, hmmmm... Memory issues?

near new laptop. i got back in within 10 minutes and no problem since.

Where you using Internet Explorer 8?

I remember this happening a while back, where closing a PM window would sometimes close all browser windows.

Never really came to any cause, though clearing browser histories and rebooting seemed to cure it.

Internet Explorer 7 (i am 99.99% sure)

Says im in chat room ATM and im not im here..coz its just happened to me too!!!!!!

You see all my abandoned games? Yeah all but about 3 are cuz of this reason

And yes I use internet explorer 8...had it happen with other browsers too though

Doesn't this happen cos of a Java error? I'm sure if you looked (or typed a shortcut somewhere - can't remember what it is or where to type it) you'd find a document starting "hs_err", or something along those lines.