HUD stats disappear on random Stars tables

[WhiteRider]

OK, let's see whether they want a log - I suspect they will despite the fact that it will be huge.
Have you tried playing less tables for a session and seeing if the HUD survives longer? This would really help narrow things down.

[Josh]

Yes, I would like to see a log. We need to know exactly what time you opened the table that didn't have the stats appear. You'll need to zip the log file in order to get it down to 6 mb (the max size you can attach to a support ticket).

[SGTJAKEY]

I just finished a 1500 hand session without this problem occurring. The housekeeping thing worked I think. I'm gonna play a few long sessions tomorrow. I'll let you know the results then.

Thanks

[kraada]

Sounds good; if it happens again though, please do submit those logs.

[SGTJAKEY]

Ok, so it happened again this morning. Twice.

The error that popped up the first time is one I haven't seen until this point. It was a windows message that said something like "fatal error windows must close PT3". I had 24 tables going at the time so I couldn't screen shot it or get an accurate read on it.

I restarted PT3 and all the stats came back up. Then a few hundred hands later, I lost stats on all my tables at once (I think) and I got this message when I tried to shut PT3 down.........

Error: Access violation at 0x005FB0B9 (tried to read from 0xFFFFFFF4), program terminated.



About logging........the only way I can capture this event is to begin logging when I start a session. This means there might be as many as 1500 hands in the log file. Is this ok?

Also, I'm doing a remote session with APerfect10 for a PAhud issue at 11am (10 minutes from now) if you wanna peek at my setup.

[kraada]

Yes, we realize the log file will be awfully cluttered, that's ok, just zip it up and it if isn't 6M or less let us know when you create the ticket and we'll provide you FTP access to upload the log and we'll attach it to the ticket ourselves manually.

I'll send Derek a message to make sure he looks at this thread, but you might want to also point it out while you're having that remote session.

[kraada]

Ok, so it happened again this morning. Twice.

The error that popped up the first time is one I haven't seen until this point. It was a windows message that said something like "fatal error windows must close PT3". I had 24 tables going at the time so I couldn't screen shot it or get an accurate read on it.

I restarted PT3 and all the stats came back up. Then a few hundred hands later, I lost stats on all my tables at once (I think) and I got this message when I tried to shut PT3 down.........

Error: Access violation at 0x005FB0B9 (tried to read from 0xFFFFFFF4), program terminated.



About logging........the only way I can capture this event is to begin logging when I start a session. This means there might be as many as 1500 hands in the log file. Is this ok?

Also, I'm doing a remote session with APerfect10 for a PAhud issue at 11am (10 minutes from now) if you wanna peek at my setup.

He's getting HUD stats disappearing randomly while playing at PS, and apprently you're doing a remote session with him shortly; I'm not sure if there's anything useful to look for while you're in there, but I figured giving you a heads up can't hurt

[SGTJAKEY]

Ok so I still have both problems you guys have been working on. APerfect10 did the remote session this morning and I just finished my 1st long session since his remote. Appx 1800 hands into my session, at appx 2:47pm (looks like 14:46:58 in the log file) the hud stopped updating all my tables. New tables showed no stats, and existing tables did not update stats.

Also, PAhud still won't update cache.

Edit: I just sent the pokertracker.log file via support ticket to APerfect10

[kraada]

Right click on the file, click Send to --> Compressed folder, and if the file is < 6M it'll attach to a ticket. If it's not, create a ticket, PM me the ticket number and I'll reply to it with the FTP information so you can upload the log to our FTP server.

[SGTJAKEY]

Pretty sure I successfully sent them via a support ticket. It might be ticket #38241.