Crash

[BigDuke66]

I had some crashes in recent time, I'm not sure if this is a scenario or engine problem as I only had crashes playing the "Nach Frankreich" scenario.
It looks like the crashes happen when I either change zoom or move the map.
Attached is the crash log, can anyone draw a conclusion out of it?

[cathar1244]

Have you tried playing with location names turned off? Not saying that must be the issue, but it appears to be a problem with a couple of other scenarios.

Cheers

[sPzAbt653]

Doesn't it appear to be a W10 problem? It certainly isn't a scenario problem.

[Shadrach]

It *could* be the memory leak with crash from the other thread, depending on how long your turns are, and how much you move the map around during your turn.

If so, turning off place names could be a workaround, or simply quitting out of the game once in a while during your turn... [8D]

I think all scenarios could cause this, but in some scenarios the growth of memory is so slow it rarely would cause any issues.

And yes, for now it appears to be a Win10 problem only.

[cathar1244]

ORIGINAL: sPzAbt653

Doesn't it appear to be a W10 problem? It certainly isn't a scenario problem.

No, damit, (just to work some German in) the problem is with the scenario! [:D]

Yeah, would have been more accurate to say it is a problem for the scenario. As to the provenance of the problem, although it manifests under Win10, I'm not sure Win10 is so much the source of the problem other than that is an updated version of an OS. I wonder if other software is having issues with Private Bytes in Win10.

Anyway, I meant it as a suggestion for BigDuke66 to try. If he is not running Win10, then no point in running the scen with location names off.

Cheers

[Lobster]

If it is a memory leak try saving and then restarting the scenario as a work around. Or even restart the game every few turns.

A couple of days ago I got a MS notification that the April 2018 version of Windows 10 will no longer be supported. Don't recall the no support date. But a new version was downloaded and installed onto my desktop. So maybe it will act differently?

[cathar1244]

Is that what that huge update was? I'm amazed it didn't break anything on my PC.

Cheers

[cathar1244]

So maybe it will act differently?

Just browsed the map of Nach Frankreich in person vs person mode. In a few minutes of browsing, Private Bytes usage moved from 246 MB to 360 MB and wasn't releasing anything. Indicates the problem may be / probably is still present.

Cheers

[Lobster]

ORIGINAL: cathar1244

Is that what that huge update was? I'm amazed it didn't break anything on my PC.

Cheers

It broke the sound on my PC. Had to jump through some hoops to fix it.

[Shadrach]

I'm still on the October 2018 update (version 1809). Microsoft are rolling out the 1903 update but it takes time for everyone to get it.
https://en.wikipedia.org/wiki/Windows_1 ... on_history

I'd say there's a minuscule chance the memory leak is caused by a bug in Windows which will get fixed in 1903, but I'm certainly going to check, whenever I get it. Probably any upcoming TOAW4 patch will be even later in coming than this W10 update [:)]

Lobster; If you have the time you could re-run the tests with Process Explorer in W10 update 1903. That would at least settle that theory. If it is 1903 you got though?

My guess is the leak is caused by some way Windows 10 handles rendering fonts to the screen, which differs from how they're handled in W7, the developers didn't account for this in the code, and didn't test for any memory leak during the beta. It might be a really subtle change related to DPI scaling or anti-aliasing of fonts for instance.

By the way I like your new avatar Lobster, it seems about right [:D]

[Lobster]

The wife is sick so I'm the nurse. This is all I have time for right now.

[cathar1244]

Shadrach, FYI, the test I mentioned above was run on v1903 of W10.

Cheers

[Lobster]

So yeah. 1903 here too. Install broke my sound so I fixed it. Fired up the PC this a.m. and black screen. Won't even post. Reseated memory and Nvidia vid card. No joy. Checked memory one at a time. No joy. Took out Nvidia vid card and the PC started. [:@]

So, now I'm using the onboard vid which is total crap until I can determine if it's just coincidence and my vid card just happened to fail after a Winblows update or if the update broke my vid card or some security update that came along with the update decided my machine was under attack. Winblows has a bad record with Nvidia stuff.

[BigDuke66]

Seeing all the W10 stuff I'm sorry to say that I run W7.

Anyhow, memory leak might still be true as the crash usually doesn't occur until I played at least into a second turn vs. the AI. PBEM was never a problem, obviously because I just did my part of the turn and then closed the game.

[Shadrach]

ORIGINAL: BigDuke66
Seeing all the W10 stuff I'm sorry to say that I run W7.

Anyhow, memory leak might still be true as the crash usually doesn't occur until I played at least into a second turn vs. the AI. PBEM was never a problem, obviously because I just did my part of the turn and then closed the game.

Windows 7 is still the best gaming OS there ever was. Too bad it's no longer supported but I wouldn't worry too much about that anyway [8D]

Problem is, others have tested with Win7 and didn't find any memory leak, so it seems to be a Win10 issue.

Another thing about the leak, is that while memory usage grows for every round played, it "resets" on every new turn, when the player changes.

The only way to know for sure is for you to run the same test with process explorer mentioned in the other thread, and post the result here.
fb.asp?m=4654077