Jump to content

JS errors and assertion failure in game lobby (on a22)


fatherbushido
 Share

Recommended Posts

WARNING: JavaScript warning: gui/gamesetup/gamesetup.js line 1990
reference to undefined property g_GameAttributes.settings.PlayerData[playerSlot]
ERROR: JavaScript error: gui/gamesetup/gamesetup.js line 1990
TypeError: g_GameAttributes.settings.PlayerData[playerSlot] is undefined
  openAIConfig@gui/gamesetup/gamesetup.js:1990:3
  updateGUIObjects@gui/gamesetup/gamesetup.js:1925:3
  setReady@gui/gamesetup/gamesetup.js:2199:2
  resetReadyData@gui/gamesetup/gamesetup.js:2223:3
  handleGamesetupMessage@gui/gamesetup/gamesetup.js:1260:2
  g_NetMessageTypes.gamesetup@gui/gamesetup/gamesetup.js:134:22
  handleNetMessages@gui/gamesetup/gamesetup.js:1609:4
  onTick@gui/gamesetup/gamesetup.js:1590:3
  __eventhandler353 (tick)@setupWindow tick:0:1
GUIManager.cpp(109): Assertion failed: "0 && (L"Tried to pop GUI page when there's < 2 in the stack")"
Assertion failed: "0 && (L"Tried to pop GUI page when there's < 2 in the stack")"
Location: GUIManager.cpp:109 (PopPage)

Call stack:

(0x55c5ac899f8e) ./../0adpublic/binaries/system/pyrogenesis(+0x5f4f8e) [0x55c5ac899f8e]
(0x55c5ac8383c9) ./../0adpublic/binaries/system/pyrogenesis(+0x5933c9) [0x55c5ac8383c9]
(0x55c5ac83a2e2) ./../0adpublic/binaries/system/pyrogenesis(+0x5952e2) [0x55c5ac83a2e2]
(0x55c5ac7a7056) ./../0adpublic/binaries/system/pyrogenesis(+0x502056) [0x55c5ac7a7056]
(0x55c5ac7ffef7) ./../0adpublic/binaries/system/pyrogenesis(+0x55aef7) [0x55c5ac7ffef7]
(0x7f657c05dfee) [0x7f657c05dfee]

errno = 0 (Try again later)
OS error = ?


Abandon

 

Link to comment
Share on other sites

Who was the host? Any chance that the host used a modded game at the time of hosting or in a previous host (persistmatchsettings) or that the client used a different set of mods than the host?

The assertion failure says that a page couldn't be popped / closed because there is no second page opened (and one page always has to remain open). I don't think we can do something there but only address the first error that triggered the further error.

Remember any circumstance? Like having clicked on the AI config button when the error occured? Or just having closed it?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...