PokerTracker

I updated to Beta 24 earlier this week and at first there were no problems. I then noticed that it was crashing periodically on Thursday and Friday (it had not crashed once since the update to Beta 23). I turned the computer off entirely on Saturday and restarted this morning. Since then it won't work at all.

1. postgres isn't starting up at all when I use PT3. It usually pops up on the list or processes when PT3 is in use but it is not coming up on that list at all today.

2. PT3 is being an incredible resource hog. Usually my CPU usage while PT3 is running is somewhere between 5 and 15%. With PT3 not running today, it's running at 5-6%. When PT3 is running that spikes up to 60-75%.

3. When I hit the button to start importing, the software recognizes that there are games running but doesn't seem to start importing hands for 10 to 15 minutes and does not actually import them all as they are running. After the 10-15 minute "warmup period", it starts to import from one file at a time. After 15 minutes more, the stats appear on the table for a few minutes and it starts to try to import hands from one more file.

It really sucks to be flying blind for the Sunday Majors.

dude just go back to beta 23 http://www.ptrackupdate.com/releases/PT ... 00.b23.exe

That fixed it. Looks like I will not be using Beta 24.

And thank you immensely for the help. Nice to know I have my stats/HUD for the rest of the day.

terellk,

I'm glad to hear that Beta 23 works well for you. If you could, though, at some point play again with Beta 24 and logging enabled (Configure --> Options --> Logging Enabled should be checked then restart PT3) and reproduce these isuses then submit your C:\Program Files\PokerTracker 3\PokerTracker.log and C:\Program Files\PokerTracker 3\PokerTrackerHud.log files to a support ticket we would greatly appreciate it. Our current priority is to fix all major bugs of this variety in Beta 24 and then release Build 4. We are hoping to have Build 4 out sometime this week, so if you send the logs in now it will get looked at ASAP and fixed for the Build 4 release.

I just now saw this response for the first time. Sorry I didn't see it in time for Build 4.