Quote:
Originally Posted by PokerStars Keith
We have a new update from the team investigating the crash bug. They believe they have a resolution but, because we can't reproduce the problem in our QA labs, we can't be certain. So, rather than issue a general client update like we did last week, we will make a special test build on .COM that affected players can download and run to see whether it has stabilized.
Within the next few hours we should have a link and further instructions, and we are asking any players on the Windows / .COM software who have been experiencing the crash bug to please try this new build and let us know how it works for your situation.
I will post again as soon as I have the download details.
Here is the link for the modified .COM build (Win/PC) that should have the crash bug resolved:
http://dev1.testpokerstars.com/excha..._COM_13519.exe
We encourage all .COM players who have been experiencing the crash/freeze problem to try playing with this client and let us know whether the crash bug is gone or still persisting.
You simply need to download and install this version, then let us know how well it works - no other steps are required.
However, it would be most helpful if you could set up your user.ini file to do extra data logging in case the problem persists. It would be best to make this simple .ini file mod after you download and install, but before you start playing with the new version - so that if there are still problems you will be capturing important data you can send to us for further research. Here are the instructions for adding the debug section to your .ini file:
http://forumserver.twoplustwo.com/sh...ostcount=25226
===========
We greatly appreciate those players who are willing to help us with this testing. We understand how frustrating it is for those of you affected, and we're sorry that the resolution is taking so long. With your kind help, it will be resolved sooner.
And, to anticipate the comments about why we need players to help us test a solution - this problem is one that we are unable to reproduce in our QA lab. Since we can't force the crash bug to manifest itself here, we have no way to verify that the code changes have cleared the bug even though the software has passed all our normal system/regression/performance tests, so we need your help. If the prior version was crashing/freezing for you and the new version does not, then we'll know for sure and we can roll it out to everyone.
===========