Author Topic: [invalid] Press E key to generate the error  (Read 1771 times)

kobe

  • Guest
[invalid] Press E key to generate the error
« on: 14 September 2010, 03:37:04 »
Press E key to generate the error: I chose the 8 AI to play against, when the station is very intense, I press the E key to the battle scenes were shot several times, suddenly an error message box, I press OK, but it Or there, when I repeatedly press OK, it still pop up. Then the game crashes. Game window suddenly disappeared.
The following screenshots, and Bug is a game information (from log file debug)

By the way: I compiled the latest SVN code and get inside the glest3.3.7-dev, I tested it. Then this error occurred.

 In [..\..\source\glest_game\game\game.cpp::Glest::Game::Game::update Line: 707] Error [bad allocation]
 In [..\..\source\glest_game\game\game.cpp::Glest::Game::Game::ErrorDisplayMessage Line: 153] bad allocation
 In [..\..\source\shared_lib\sources\sound\openal\sound_player_openal.cpp::Shared::Sound::OpenAL::StreamSoundSource::update 224] Restarting audio source because of buffer underrun.
 In [..\..\source\shared_lib\sources\sound\openal\sound_player_openal.cpp::Shared::Sound::OpenAL::StreamSoundSource::update 224] Restarting audio source because of buffer underrun.
 In [..\..\source\glest_game\game\game.cpp::Glest::Game::Game::update Line: 707] Error [bad allocation]
 In [..\..\source\glest_game\game\game.cpp::Glest::Game::Game::ErrorDisplayMessage Line: 153] bad allocation
 In [..\..\source\shared_lib\sources\sound\openal\sound_player_openal.cpp::Shared::Sound::OpenAL::StreamSoundSource::update 224] Restarting audio source because of buffer underrun.
 In [..\..\source\shared_lib\sources\sound\openal\sound_player_openal.cpp::Shared::Sound::OpenAL::StreamSoundSource::update 224] Restarting audio source because of buffer underrun.
 In [..\..\source\glest_game\game\game.cpp::Glest::Game::Game::update Line: 707] Error [bad allocation]
 In [..\..\source\glest_game\game\game.cpp::Glest::Game::Game::ErrorDisplayMessage Line: 153] bad allocation
 In [..\..\source\shared_lib\sources\sound\openal\sound_player_openal.cpp::Shared::Sound::OpenAL::StreamSoundSource::update 224] Restarting audio source because of buffer underrun.
 In [..\..\source\shared_lib\sources\sound\openal\sound_player_openal.cpp::Shared::Sound::OpenAL::StreamSoundSource::update 224] Restarting audio source because of buffer underrun.
 In [..\..\source\glest_game\game\game.cpp::Glest::Game::Game::update Line: 707] Error [bad allocation]
 In [..\..\source\glest_game\game\game.cpp::Glest::Game::Game::ErrorDisplayMessage Line: 153] bad allocation
« Last Edit: 14 September 2010, 03:44:21 by kobe »

titi

  • MegaGlest Team
  • Airship
  • ********
  • Posts: 4,240
    • View Profile
    • http://www.titusgames.de
Re: Press E key to generate the error
« Reply #1 on: 14 September 2010, 09:58:52 »
This might be a interisting bug! Ultifd and I had an error yesterday while playing multiplayer maybe its the same bug!

Kobe said this bug is reproducible. You just need lots of fighting and dying action on the screen and press e key several times. than it happens.
This sounds a bit like cache problems again to me, but thats just an idea. If its related to the cache it can also be the problem we had, because memory problems are always a very likely cause for out of sync problems.

Sadly I lost all the logs because I accidently started glest while he was still compressing the logfiles ...


« Last Edit: 14 September 2010, 10:14:14 by titi »
Try Megaglest! Improved Engine / New factions / New tilesets / New maps / New scenarios

ultifd

  • Airship
  • ********
  • Posts: 4,443
  • The Glest Video Guy :) The one and only. :P
    • View Profile
    • My Youtube Channel
Re: Press E key to generate the error
« Reply #2 on: 14 September 2010, 21:45:04 »
Sadly I lost all the logs because I accidently started glest while he was still compressing the logfiles ...
You mean he=you. Although, unfortunately I lost my log that way too. But it wouldn't have helped anyways.

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Re: Press E key to generate the error
« Reply #3 on: 15 September 2010, 05:58:53 »
I tested a new testing mechansim (letting the AI play against itself over the network) using Windows XP and Linux and no out out synch issues. The AI was mega vs mega and in the end the Norsemen beat Tech (while i watched both screens to ensure every movement was the same on both platforms).

ultifd

  • Airship
  • ********
  • Posts: 4,443
  • The Glest Video Guy :) The one and only. :P
    • View Profile
    • My Youtube Channel
Re: Press E key to generate the error
« Reply #4 on: 17 September 2010, 00:57:19 »
Are you saying it is resolved? Or...?

ultifd

  • Airship
  • ********
  • Posts: 4,443
  • The Glest Video Guy :) The one and only. :P
    • View Profile
    • My Youtube Channel
Re: Press E key to generate the error
« Reply #5 on: 17 September 2010, 01:00:53 »
So you updated to SVN head and got the exact same problem?

-Archmage-

  • Moderator
  • Dragon
  • ********
  • Posts: 5,887
  • Make it so.
    • View Profile
    • My Website
Re: Press E key to generate the error
« Reply #6 on: 17 September 2010, 02:04:40 »
Kobe stop saying that, the devs are working, and on top of MG they have a little thing called a life. :|
Egypt Remastered!

Proof: Owner of glest@mail.com

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Re: Press E key to generate the error
« Reply #7 on: 17 September 2010, 06:00:51 »
Kobe we are busy, and i don't want to be rude but you have not been patient. I made an attempt to try to fix your bug (that I cannot reproduce) and checked it into svn (it is included in beta 2)

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Re: Press E key to generate the error
« Reply #8 on: 17 September 2010, 16:12:18 »
Your log file has nothing to do with pressing E to save screens. You are running out of memory and this is why you get these errors. What is your memory usage (free memory and used memory)?

You can try disabling some performance caches by editing glestuser.ini and adding these:

Quote
MaxExploredCellsLookupItemCache=1
UseQuadCache=false

 

anything