Access Violation during battle end

[sloanjh]

Just had an access violation during the battle end stuff (immediately after the "no ships in contact, time limit expired dialog" and before the battle summary).  I had a lovely screen shot of it, but unfortunately I overwrote the file with the screen shot below and couldn't get it back.  The routine was something about evaluate damage or maybe save damage.  I looked at task manager and memory seemed fine.  After I was in the summary dialog I tried to pull up the ship details and got the error below.  Note that the offending ship is the same one, so it looks like that one ship was somehow corrupted.





Note the task manager saying memory looks ok even though the dialog says out of memory.  I then tried looking at the log of the offending ship, and got a similar error, and the log screen didn't have a white text box - the grey filled it.  This was the case for all the other ships I tried to look at the log for.

I then tried a save/restore.  I think (but am not sure) that it errored again one more time in the save.  Unfortunately, when I came back it I couldn't reproduce the error - it ended clean.  I did an exit again (apologies - I meant to attach the 1st save file but forgot) - the save file attached is from right after exiting the battle screen.



When did you start the game - 1900



What nation were you playing?



UK



Were there any start options that were not the default?



Large, build legacy, bumped to highest difficulty in 1st battle



Describe the issue in detail.

What were you doing when the bug occurred?

finishing battle
What did you expect to happen and how was the result you saw different than you expected.

See above

Can you describe how to reproduce the bug?

See above

What version of the game were you playing (v1.00, v1.01, etc)? 1.04 (started game in 1.00)

Attachments:

Game1e.7z (362.02 KB)

[sloanjh]

Pretty sure I just had it happen again.  Here's the 1st error:




This was a coastal raid by me.  After the summary popped up, I tried to go to ship details and got the exact same access violation (including addresses).  DD Catapulte is a French (enemy) DD.  In this case it only took like damage from one light hit (the previous time the offender had been sunk).  I was able to open a ship (NOT Catapulte) and see its log.  When I opened Catapulte and tried to see its log, I got "Access violation at address 004028A9 in module 'RTW2.exe'. Read of address 1004FFFD." (not posting screen shot because I want to post a save file) and did not see the log.  When I clicked for the log again I got "Out of Memory".  Task manager looked ok, but when I look at processes the working set for RTW2 is almost 840MB.  If I click more I keep getting out of memory.  Closing Catapulte and trying another ship results in a grey log panel when I try to look at it.

When I exit the summary and hit the save button, I get another dialog: "Error in SaveGameShipData procedure! Division20 DD Catapulte Out of memory (the working set is still essentially the same).

I've attached the result of that save, WITHOUT HAVING EXITED THE BATTLE YET.  Note that when I did this the last time, reloading the save and re-going through the end stuff did NOT result in the error.

Hope that helps...

Attachments:

Game1f.7z (381.52 KB)

[oldpop2000]

You could try going to Data Execution Prevention, turning on DEP for all programs and services except those then go to the game and put the name of the exe file in that and add it. Now see if that fixes the problem.

To find DEP, go to control panel home, click on Advanced system setting, click on performance settings,now click on data execution prevention.

[rimbecano]

Jun 19, 2019 21:58:15 GMT -6 sloanjh said:

When I clicked for the log again I got "Out of Memory".  Task manager looked ok, but when I look at processes the working set for RTW2 is almost 840MB.  If I click more I keep getting out of memory. 

32-bit programs like RTW can only use 4 gigs at best, and depending on how they were compiled, as few as two. The working set is how much of the program's memory is being actively used. So this kind of behavior is not at all unexpected for a memory leak: the program keeps forgetting to free memory that it's done using, so when it needs memory for new data it keeps asking the OS for more instead of reusing memory it already has that it isn't using. Eventually the OS has given it the full 2-4 gigs that it can use, and the next allocation attempt throws an OOM error, but because it's not using most of the memory assigned to it, the working set is still short of the 2-4 gig limit.