Got a crash log here(Updated)

Program aborts? Network configuration? Graphic errors? Bugs? Post your question here.
posted on December 2nd, 2010, 6:40 pm
Last edited by 086gf on December 14th, 2010, 6:27 pm, edited 1 time in total.
I got this last night. Tried to repeat it but didn't so im not sure what happened.

Attachments

exceptArmada2.txt
(61.41 KiB) Downloaded 186 times
posted on December 2nd, 2010, 9:13 pm
what were you doing at the time? starting a game?
posted on December 3rd, 2010, 5:58 pm
Yes I was. Dominion(Breen) vs. Dominion(Hard?). Though like I said it was a one off so I don't know.
posted on December 14th, 2010, 6:27 pm
Got another one here. Almost exact same situation(clicking build button on starbase) except that I was Taq against hard Klingons and it was a few minutes into the game.

Attachments

exceptArmada2.txt
(84.42 KiB) Downloaded 220 times
posted on December 14th, 2010, 10:13 pm
this crash bug exists a while now. problem is that i cannot reproduce the problem yet which makes it hard to debug.
what i know that it occurs when clicking on a build button, but that's it. if someone discovers a way to repeatable reproduce the problem, please let me know.
posted on December 14th, 2010, 11:33 pm
Doca, seems a bit odd that a button in game would cause a mission load. Perhaps there is some aliasing of buttons going on? I've not really looked around the button system in depth, but maybe the ID of a button in game and the button back in the menu are clashing and the wrong callback is firing.
posted on December 15th, 2010, 9:20 am
Last edited by DOCa Cola on December 15th, 2010, 9:26 am, edited 1 time in total.
no no, look further down at the end of the log. there is more than one crash report in this file. the latest report is at the bottom.
it is not a crash in 'stock' code but more in my code for the increased number of available buttons. it is a problem with the buttons actions. not sure, maybe i forgot to reset them at some point, but after looking multiple times at my code i haven't found anything yet that seems to cause this. problem is that i wasn't able to reproduce it yet for debugging. i am overlooking something there.
posted on December 15th, 2010, 9:49 am
Oh yes, there are more than one. Oops. I did actually manage to get it to do the button crash, will try to figure out how again tonight.
Reply

Who is online

Users browsing this forum: No registered users and 27 guests