Loading Profile...
Poker Copilot V2 Build 13 Meltdown
Things started off well, but at a certain point in today's session the program started slagging my whole system. I was playing on four cash tables at once, and everything seemed to be fine for the first 500 hands or so. At about that point the whole system got slower and slower, the entire OS was affected. The first sign of trouble was a five second disconnection from FT's game server, and then gradually the response times for all programs went through the floor.
I was running Safari, iTunes, Full Tilt and Poker Copilot V2 on a Mac Mini 2Ghz Core 2 Duo, Leopard, with 2GB of RAM. Switching between applications got slower, then there were more disconnection lags. I tried stopping and starting the HUD and that didn't help at any. It took a few seconds after quitting PCoP for things to return to normal.
I fired up V1 and that worked great, as always. I didn't try re-starting V2 again, I didn't want to risk it. Seems like there was a memory leak, but then again it's impossible to say exactly what was grabbing so many processor cycles from the OS. There weren't many slices left for core processes or other programs, that's for sure.
I was running Safari, iTunes, Full Tilt and Poker Copilot V2 on a Mac Mini 2Ghz Core 2 Duo, Leopard, with 2GB of RAM. Switching between applications got slower, then there were more disconnection lags. I tried stopping and starting the HUD and that didn't help at any. It took a few seconds after quitting PCoP for things to return to normal.
I fired up V1 and that worked great, as always. I didn't try re-starting V2 again, I didn't want to risk it. Seems like there was a memory leak, but then again it's impossible to say exactly what was grabbing so many processor cycles from the OS. There weren't many slices left for core processes or other programs, that's for sure.
I’m bummed
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?I realized this morning that the issues I experienced could be due to Apple's implementation of Java, rather than Poker Copilot V2. However, I have never experienced these sorts of problems using V1, even when playing multi-table sessions of more than a thousand hands. Yesterday I played another 1,000 hands with V1 after the V2 shutdown with no problem, so I don't really have a clue what's causing the failure, Apple or the V2 architecture. Would V2 work better with MySQL instead of a Java DB? Enquiring minds want to know lolz.
Thanks for all your hard work, I know it will come together at the end of the road. This is Alpha warez and if it doesn't crash your goals weren't aggressive enough ;-)
I’m concerned
