Bombardment Bug

[John Lansford]

Using version 1.2, I sent a task force of cruisers and destroyers to bombard the Shortlands. After shooting up some destroyers, they then began the bombardment routine.

Except instead of the usual screen showing the bombardment, it went to a ground attack screen involving the Kanga Force and a Japanese regiment. My task force took a few hits from 3" guns, and the summary looked correct (hits on the port, airfields and support facilities), but it looks like the combat screen routine is messed up.

[Bernd Hesberg]

This behaviour has been reported earlier, and it's on the list. AFAIK a memory leak is causing this, but since it doesn't get fixed with v1.30 I guess we'll have to wait for the next patch. It's not a game breaker, just messing up the display.

[XPav]

"A memory leak is causing this."

Based off of what?

[Bernd Hesberg]

You may read Ross' reply in the following thread

showthread.php?s=&threadid=23596

Beside those posts I've had some correspondence via email. So I'm absolutely sure that this bug will be hunted down, but I don't know any details.

[XPav]

I don't see how this could be a memory leak.

What it looks like is a buffer being reused without clearing it.

But that's not a memory leak, its a different problem.

Consider this part of my fight against every single technical problem being labeled a "memory leak".

[Bernd Hesberg]

Hi Alex,

I didn't think that using this particular term would hit your tender spot.

Since English isn't my native language, and you need specific knowledge to translate technical terms, I may have misunderstood or misused it. Of course, you may blame me for repeating it without prior checking if this term would be appropriate. But maybe you can give me a competent definition for memory leaks ?

[XPav]

Memory leak is what Matrix says. I just don't buy it.

A memory leak is when the program goaes "Hey! Operating System! Give me some memory to play with!"

It doesn't give it back, and forget that it has it.

Next time the program comes back to the same thing, it goes "Hey! Operating System! Give me some memory to play with!".

Do this enough from one program with big enough chunks of memory on the system and you can get the thing to start using so much memory that the OS has to really start working, swapping memory out to disk, etc etc.

The problems all go away when the program is completely terminated, or worse comes to worse (if the program really started doing some stupid things), when the computer is rebooted.

Memory leaks are a common problem when writing code in C and C++. The sad part is that there's so many, many ways to avoid memory leaks that we shouldn't have to deal with them.