Zeoslib Portal

i have a big problem with zeosdbo-6.1.5-stable.
increase memory usage with any datasets used under firebird 1.0/5.
i think is a bug with free mem of some pointers, on close datasets or recreatign inutils pointers at open. on a simple dataset with 2 columns an 2 records, numbers of non free pointers increase by 85. this number depend by column number and data type (i think).
i have installed zeosdbo-6.1.5-stable on delphi 4 with 2 patch, from sourceforge.net.
is anybody who have this problem? ideeas? solutions?
thanks.

I have this problem too with MSEide and ZeosLib last trunk (Testing Branch). Memory increase every 4 kb, without another operasion, just move record with tdbnavigator.

Hi Mark, you can see it with dbnavigator, and move record more times, and you can see at task manager, memory is increased.

regards

Hi Wahono,

I'm very sorry to tell you I'm not a memory specialist. The more, here FPC is involved. I had a look at your previous question but also without success.
I'm not going to tell you 'it's FPC'. But to debug it for your case, you'll have to do it yourself. Or even better : find a FPC expert who can do it for you (/us). Remember : I'm not the Zeoslib writer. Just a humble forum moderator and patches applier.

Mark

already i found somethings. i reduce live and unused pointers from 85 to 36 in my test application. but in this moment i'm in inpass. i don't find where is others. anyway, this is a bug in base classes who inherited in most dataset classes. in my opinion is an impotant bug, specialy when it work on large databases in real-time. in most version of zeos lib this bug exists. if you are interesed u can run any application who use zeos lib and firebird (4 ex - i belive this bug is present whith other datasets type) and see in task manager how it increase memory usage of PC at every refresh, open, close... activity. u can try IB_SQL, is one of application who have this bug. in time aplication will generate a low memory error and crash.

all the best.

Can you tell which changes you made? I don't patch 6.1.5, but maybe we can check if this is still useful in 6.6 version.

Mark

it's two types of misstakes:
- don't free base pointers used in class instaces (in my app i reduce peak from 100+ to 6) - visible when close app (sometimes app generate an error on close)
- don't free temporary used in misc operations (open, close, refresh... so on)
i need a complette docs for 6.1.5 ver. pls.
in this moment i have a lot of changes not commented. when i finish some works i will post a patch.
if u have a docs about 6.1.5. send me one, pls.

thanks.