memory error

[daj]

I seem to have more than my fair share of anomalies - I protest!

I blame the other weather software you are running!
(only kidding -- I know the two have ran together for a while)

[steve]

I blame the other weather software you are running!

Yes, me too

But this is a real, reproducible problem, and not specific to you, Dave(NZ). Unfortunately it is probably another bug in the chart component, so getting a fix is going to take some time. Basically, this version of the chart component comes free with Delphi, and is effectively unsupported. Fixes are made available infrequently. To get basically the same functionality, but with support from the company that writes the component (Steema) and more frequent fixes, I'd have to pay 199 USD.

[daj]

Why don't we start a fund to allow you to buy the new charting tools? I'm sure we can get to $200

[steve]

Why don't we start a fund to allow you to buy the new charting tools? I'm sure we can get to $200

Donations are still trickling in, so I should buy them from that. It's just that I have already spent several hundred pounds on the new version of Delphi, and just over a hundred on some new components (including the new gauge). I'm not sure it's fair to ask people to pay more just to get bug fixes; and there's no guarantee they will fix the bug quickly anyway. It wouldn't be so bad if we got extra functionality for the price, but they would basically be the same charts.

I've produced a very simple test case that reproduces the bug. It doesn't require the GDI+ that the new charts use, or anything fancy. A simple line chart does it. Grabbing a bitmap from the chart and then hiding and showing it uses up memory. I'll report it and see what happens; they may have a work around.

[daj]

Ok, you're the boss. I am concious that you have already spent a fair amount of cash on new software, and you continue to put a lot of time and effort into the product.

Keep the idea in the back of your mind -- for example, 20 people putting in $10 is not a big ask (in my view anyway)

[steve]

I've replaced the chart's built-in code for grabbing a bitmap with my own code, and that seems to have removed the memory problem. New build to follow shortly.

[DaveNZ]

I've replaced the chart's built-in code for grabbing a bitmap with my own code, and that seems to have removed the memory problem. New build to follow shortly.

Thanks for the fast action as usual Steve! Have downloaded the new build, and can't get the RAM to rise much above 26MB anymore

[daj]

Thanks for the fast action as usual Steve! Have downloaded the new build, and can't get the RAM to rise much above 26MB anymore

Me too -- I managed to push it to nearly 40mb, somehow! But can not get it to go above that.

Well done Steve -- brilliant turnaround on the problem.

[wd40]

Mine is floating between 13.4 and 13.5 without a graph.
21.7 with the graph window open.
Around 22 with select a graph with all winds selected.

Randy

[steve]

It seems that the memory leak wasn't a memory leak after all. The memory is being freed, it just stays 'reserved' but is available for Windows to reallocate any time it wants.