GDI functions & Init problems?

[Mike Lobanovsky]

I will try indexbase 0 & 1 and what is the difference ...

Hi,

On default, O2 assumes arrays start at index 1. indexbase lets you change this default behavior. If you are using arrays that start at index 0 but you haven't specified indexbase 0 then in the For/Next loop that Charles showed, O2 may either i) skip working for arg0[0] and develop memory leaks here (at best), or ii) crash completely (in the worst case). Either way, O2's behavior will be, technically speaking, undefined.

Try to always match you arrays with an explicit declaration of the respective indexbase. We will all be getting significantly fewer headches if we do it too. Don't rely on the language defaults; be very specific about everything you do in your code.

Do not use string assignments that generate temporary strings in For/Next, While/Wend, Do/End Do loops! OxygenBasic cannot automatically collect temporary string garbage generated internally in such loops!

[Aurel]

Mike i check everything yesterday 4  times...
and download latest realease and problem is present
and i repeat....how then work fine with older dll without mem leak
dll which work is from old PeterW version oxyBasic.
 

[Charles Pegge]

Hi Mike,

If strings are dim'ed before the loop then all is well.

But when dim'ed or auto-dim'ed inside a loop, the string's reference will be reset, and a new entry will be made on the Garbage Collector list. This is tolerable, though undesirable, for small iterations on local strings, but otherwise builds up a mountain of uncollected garbage.

Apart from global and local string GC lists, there is a list for temporary strings, which are to be freed after an expression.

Hi Aurel,

I've now tested all O2 string functions, and have not detected any leaks. However I detected one issue with local string arrays getting logged to the global GC, but all your arrays appear to be global anyway.

Oxygen DLL Update (200k)
http://www.oxygenbasic.org/o2zips/Oxygen.zip

[Aurel]

yes Charles all my arrays are global and there is no any direct imapact on interpreter loop.

[JRS]

@Aurel - Do you know where in your interpreter the leak is occurring? Is your claim based on "this is the memory available when I start the program and this is what it increased by once it ended"? Are you using any type of debugger in troubleshooting the issue your having? I guess what I'm asking, is this more than just a feeling you have or can you post a code snippet of it failing?

[Aurel]

John
open task manager and run ...then you will see how memory using grove...
simple ...
what kind of debugger 

[JRS]

John
open task manager and run ...then you will see how memory using grove...
simple ...
what kind of debugger 

Oh, I got it. You have no idea or proof O2 is leaking memory other than task manager which accumulates all processes used memory.

You need to do better than that if you want to call yourself a programmer.

[Aurel]

You need to do better than that if you want to call yourself a programmer

oh tutie-frutie managero 

enough for me
sorry but i am not creator of o2 , so how i know what is where 
SLS   

[JRS]

You need to do better than that if you want to call yourself a programmer

oh tutie-frutie managero 

enough for me
sorry but i am not creator of o2 , so how i know what is where 
SLS   

Unlike many of the Windows offerings, O2 comes with source and the only limitation is your curiosity and willingness to learn.

[Charles Pegge]

Hi Aurel,

I've made some progress, leak hunting in Ruben3.

 I traced down to a dropped optimization affecting instr(). When the optimization was restored, the memory leak disappeared, (testing with fern.RUB).

However, this only masks the underlying problem, adversely affecting instr(). So further investigation is required.

14 May 2015:
http://www.oxygenbasic.org/o2zips/Oxygen.zip

[Aurel]

Hi Charles
I am glad that you find where problem is ...so
instr()...
i really don't have a idea what might be wrong when old release work as expected.
i must say that i have one experimental version of ruben written in old Emergence Basic
where i have only few commands including forLoop ...Diffrence...
ufff is BIG...
that version take only 2300k and there is no any sign of mem leak.
String operations in EB are very good BUT speed of execution is better with o2 
I don't have Power Basic but from what i read and what i can see in Eros work (tB)
i can say that i would like that o2 have such a speed with strings..
all best..

[JRS]

Good job Aurel sticking to your guns and blowing off people like me saying it must be you. 

I don't have Power Basic

You would probably have better luck finding a copy on the torrents then getting anyone at PowerBASIC to sell you one.

[Aurel]

Yes Charles
 tested new dll and it seems that mem leak gone
mem usage is fixed to 4088k on my computer and work very fast.
Of course i will test tomorow whole code of ruben4.