Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception has been thrown by the target of an invocation #15

Closed
GrantBartlett opened this issue Dec 4, 2016 · 6 comments
Closed

Exception has been thrown by the target of an invocation #15

GrantBartlett opened this issue Dec 4, 2016 · 6 comments

Comments

@GrantBartlett
Copy link
Member

Exception has been thrown by the target of an invocation
https://forums.cncnet.org/index.php?topic=6922.0

Log: https://docs.google.com/uc?authuser=0&id=0B8gSFgpT3dl3UFY4dnpOUWZjS0E&export=download

@Rampastring
Copy link
Member

"Exception has been thrown by the target of an invocation" doesn't tell anything, but you can take a look at the log to see the inner exception that is the actual problem. In this case it was an out-of-bounds array / list access somewhere in the code.

Could use more information on what was going on when it happened.

@GrantBartlett
Copy link
Member Author

"The first time it happened right after game end, the second time I believe it randomly happened in game lobby. I try pay attention to it next time when I get it again."

@GrantBartlett
Copy link
Member Author

I beleive I've just got this error now.
error

ClientCrashLog_11_12_2016_13_47.txt

@Rampastring
Copy link
Member

Crashed in CnCNetGameLobby.Channel_UserAdded(object sender, ChannelUserEventArgs e), on

if (Players.Count + AIPlayers.Count > MAX_PLAYER_COUNT)
AIPlayers.RemoveAt(AIPlayers.Count - 1);

Based on the screenshot and investigating the log, player "mixo" had left the game earlier, but afterwards the game host had still sent a player options message that had "mixo" in it, leading the client to have 8 players in the internal player list. When the new user joined, Players.Count reached 9, which is above the maximum of 8 and caused the client to crash.

@Rampastring
Copy link
Member

Potentially fixed in 0965180

@Rampastring
Copy link
Member

Assumed fixed. Re-open or create a new issue if something similar is still seen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants