leemi / androminion

Automatically exported from code.google.com/p/androminion
0 stars 0 forks source link

application crashes in a very long game #313

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
My last random game used Courtyard, Chapel, Scrying Pool, Menagerie, Lookout, 
Nomad Camp, Remake, Monument, City, and Margrave.  I have played this set 
several times, and I can make the game crash most times by prolonging the game. 
 I use City and Monument to get my points without buying anything, and I use 
Margrave and several Scrying Pools every turn to hinder my opponents.  I can 
easily get over 100 victory tokens, but the game tends to get slower and 
eventually crash.  This card set is still my "last played" set so I can 
reproduce the problem again if that will help with diagnosis.

What is the expected output? What do you see instead?
I expect the game to continue without slowing down or crashing.

What version of the product are you using? On what operating system?
2.02, Android 2.3.3, HTC Evo 4g

Original issue reported on code.google.com by paulj...@gmail.com on 26 Mar 2012 at 8:03

GoogleCodeExporter commented 9 years ago
I haven't been able to reproduce this in the latest build of Androminion on my 
Galaxy Nexus (4.0.2).  I tried some crazy things like 100+ cards in hand or in 
play, and I couldn't break it.  The Evo is a pretty beefy phone, so I'd expect 
it to perform similarly well.  I also don't remember seeing anything like this 
on my Droid.  The issue might be related to the total number of turns played or 
something.  

Original comment by August.D...@gmail.com on 31 May 2012 at 8:22

GoogleCodeExporter commented 9 years ago
I just reproduced the crash with version 2.04.  This happened after 127 turns, 
which is a suspicious enough number.  The log is attached.

Original comment by paulj...@gmail.com on 30 Jun 2012 at 4:18

Attachments:

GoogleCodeExporter commented 9 years ago
I was able to drive it up to 167 turns without crashing in 2.05. Maybe a memory 
leak somewhere?

Original comment by tkdenni...@gmail.com on 17 Aug 2012 at 3:50