Random C++ Debug Crashes

[sython]

Getting this randomly...sometimes logging in, sometimes fighting...


any suggestions?

[kjLotus]

find a way to reliably reproduce it and then let me know the steps

[sython]

could this sort of thing occur if there was a problem with the sql database? ie. missing field in 1 of the tables, or a missing index.
as i transferred over my character tables from my old server which was a couple of months out of date. i did double check to make sure everything existed etc....

But i just recreated the error, when i created a new account, and created a new character.
Then when i log in, with that character, i get that error.
if i log in with one of my other accounts, and characters its fine.
The the time it occurred was when my kids where playing together... seems when more than 1 player was on...

that's why i was asking about possible missing fields causing the issue~?

[kjLotus]

could this sort of thing occur if there was a problem with the sql database? ie. missing field in 1 of the tables, or a missing index.
as i transferred over my character tables from my old server which was a couple of months out of date. i did double check to make sure everything existed etc....

if your server code now is new and your tables are from back then, then yea, that's probably the problem (i've recently added a bunch of columns for automaton stuff in char_pet and chars, for example)

[sython]

could this sort of thing occur if there was a problem with the sql database? ie. missing field in 1 of the tables, or a missing index.
as i transferred over my character tables from my old server which was a couple of months out of date. i did double check to make sure everything existed etc....

if your server code now is new and your tables are from back then, then yea, that's probably the problem (i've recently added a bunch of columns for automaton stuff in char_pet and chars, for example)

Thanks, gives me somewhere to start looking for the issue...

[kjLotus]

running it in debug and hitting retry when that happens and then looking at the call stack should pinpoint that pretty quick