Tech Glitches on New Table Load

[DrewMan]

I got knocked out of two tourneys today because of the "upgrades" to the site. This isn't so much about lost chips as the loss of enjoyment and fun on the site. It is free and just for fun, but when you are in the running for a win and site bugs cause a loss, it makes it less fun, and so I don't want to play. The main issue is with the time it takes to load a table now, and with the site kicking me out of the browser when windows open or close. The new code is just less stable.

Here are the particulars.

I was in the weekly mammoth and doing well late into the tourney. I opened the lobby to see where I was and it was frozen. So I closed the window and reopened the lobby and it kicked me out of my table and crashed the browser. Normally I would be like, OK, no problem. I'll just reopen the window. Losing a hand I was in with a playable hand, but that's the breaks. But I reopened a browser window, went to the site, opened the lobby and the tourney, and it tried to open the table, and LOADING, LOADING, LOADING.... until it was too late and I was kicked from the tournament.

Similar thing happened on the invitational tourney. I was down to head-to-head with Azza after beating out Roo, Danzi, Donkey, Dean, and was ahead and psyched. and I get KICKED. I was playing every hand and just got kicked.

SUCKS

This isn't about chips, its about fun...

Makes me not want to play here...

Lava, can we go back to simpler, quick to load tables. Or can you get the code more stable. Is the chat and links to other games really necessary on the table page? Are you getting enough click-through to warrant the people you'll turn off with unstable code?

Please consider it...

- DrewMan

[TheTexan]

This is the first note of this. Aside from the normal solution suggestions about cookies and temp files and such I would ask if you are running MS Windows and if so, do you have automatic updates turned on? If so that could be the issue. If you can roll back your system to an earlier date (prior to the most recent updated) this may address the problem.

PM me with the particulars on what you are running and I will try and assist.