??????
You are not logged in.
Pages: 1
Sometimes on OS X Yosemite when just playing and moving the two cursors around the game hangs, beachballs and never responds. It ends up crashing at the end resulting in one disconnecting from the server and loosing your bet. (I just lost around 3.20$ ;_;) Here is the crash log OS X threw me:
http://rly.moe/crash
Offline
Did you actually lose $3.20? That should have put you in the bottom 4 on the profit leaderboard (unless you were number 1 or 2 on the leaderboard before that and I missed your climb) and I think they look the same as the last time I looked down there.
Edit: Nevermind, just saw the bottom of the leaderboard change, maybe it just hadn't updated yet.
Last edited by Asminthe (2014-11-23 01:35:51)
Offline
Oh, I bet the game just hadn't finished closing up yet, so your balance was still considering the money on the table to be unavailable!
Offline
When you time out of the previous game the remaining coins would be returned. What surprises me is that it doesn't immediately cancel the previous game as invalid when you logged in a second time.
Offline
Offline
Yeah, when you reload the game, it gets the balance first, which doesn't currently kick you from the old table. Then it loads the list of games, which DOES kick you. Of course, the balance is already loaded before that, so you see the old balance one time. After re-loading the list of games, the balance is fetched again. I should probably change it so that fetching the balance itself is one of the things that kicks you from the game.
About the crash:
I'm sorry that this happened. I LOVE that MacOS actually produces real crash reports. Sadly, this one doesn't actually show what happened, except that the game got into an infinite loop. I didn't know the OS would actually catch this and kill the process, but that's cool! The stack traces don't show what was actually stuck, for some reason.
If you're just dragging sliders around, the the game is doing nothing else, so maybe there's an infinite loop in the slider-repositioning code. There should be no network operations while you're doing that, for example. One thought: the audio thread could also be involved, because maybe your time is running out and the chime is trying to play when there are 10 seconds left.
Do you happen to have a recording that shows one of these crashes? Please email it to me:
jasonrohrer@fastmail.fm
Offline
There's a chime to indicate 10 seconds left? I've only ever heard a rare chime right at the beginning of a turn (I think typically the 3rd turn) and I'm wondering what it indicates.
Offline
Chimes happen:
--When waiting for the opponent, right before the game starts (a "game is starting" chime)
--When you've been waiting more than 10 seconds for your opponent's move, and the move finally comes through (unless that move has coin-movement sounds that will play---no chime needed then).
--When you have less than 10 seconds left to make your own move.
Offline
Hey, I also got a crash when moving cursors around. Also running Yosemite.
Offline
Can you play a short session that demonstrates this and then send me the recordedGame file? I can watch the recording on my end and maybe figure something out.
jasonrohrer@fastmail.fm
Also, did Yosemite produce any kind of crash report or log that you can send me? I know that MacOS is sometimes pretty good about that.
If you're willing to delve a bit deeper, email me, and I can walk you through the steps of running the game inside a debugger that would catch the crash once and for all and give solid info for fixing it. It would be REALLY helpful! I don't have access to a machine running Yosemite.
Offline
Pages: 1