Andi47
Overlord
- World: zz1, de8
- Browser and Version: 1.40.27602 (20.11.2014 11:04), Andi47 (73349), zz1, en_US, WIN 15,0,0,223, Windows 7, Firefox/33.0, 1920x939, DirectX9Ex (336 MB VRAM)
- Overview of the bug: When doing several consecutie battles in GvG, there is possibly a memory leak, and eventually the sound will fail to play.
- Screenshots: n/a
- How often this occurs: EVERY time (just do enough battles!)
- Urgency: medium (or high if you want to reduce server load caused by players forced to repeatedly relog)
- Preventative Actions: relog after doing ~10-15 battles in a row
- Summary: how to reproduce
1.) have lots of units of the age where you want to fight in GvG and enough goods to lay siege
2.) relog to get to a defined starting point
3.) go to GvG map. If not yet placed, place a siege to a sector your guild wants to conquer (or ask a guildmate to do so)
4.) do consecutive fights. (i.e. fight, select new units if necessary, fight again, etc.) It doesn't matter whether you finish/win the battle or click "surrender". (the latter would be faster for testing, it seems just to be important that the battle map is loaded and shown). Have an eye on the memory use of the flash player. I guess you need to do approx. ~15-20 battles for testing the sound issue and ~30-50 battles for testing whether the game will crash. Please don't test only with super-mega-high-end computers, but also with computers affordable to average players.
Result:
I did not watch the memory use this time, so I'm not sure whether the increase observed before the implementation of 1.39 was caused by GvG or by the memory leaks which were fixed with 1.39. But even with 1.40 after a certain number of battles (~15-20, no matter whether you finish or surrender them) you will no longer hear any sound (like walking/driving or shooting units). I have not tested since quite some time, but a few versions ago, continuing to fight more consecutive battles after the sound failed would eventually cause the game to crash.
Reloading (e.g. after the sound failed) resolves the issue - for a short while.
. - I have performed a quicksearch of the forums using a select few keywords relating to my bug to see if it has already been reported: I think this has been mentioned somewhere in one of the feedback threads, but I was not able to find it.
- Have you tried fixing it by using these methods?: relogging resolves the issue - for a short while.
Last edited: