Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2006-07

AW: AW: MemoryLeak with AS Operator

5 messages · 5 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Helmut Hartl

Hello Joost,

Maybe I should be a bit more informative:

We (I) am the currently technical maintainer of ZEOS Database Library. We donate some of our work to the ZEOS DB Library.

We are currently stabilizing it and using it in a
carrier grade billing system for a VOIP Telco Provider.

We have a 7/24 SLA with an uptime guarantee of 99,9% per month for the daemon applications. (Linux Server side built with Lazarus and FPC) The client side on windows is crossplattform and is built with Delphi. You see we have a strong belief in Object Pascal. :-)

We closely follow the SVN Versions of FPC so our interest is to help FPC to be and to become ultra stable.

In our testsuite test we saw now that there is a bug in compiler/rtl memory management. We pinpointed the
problem with a demo app and bug report.

Our interest is to help fixing it as we won't want to search and change our code in about 90.000 lines of code, nor we wont want to make hybrid compiler versions as we do at the moment.

We regularly test our whole code against the fixes branch and the 2.1.1 branch and use a hybrid 2.0.2 + dataset patches for our release.

A new ZEOS library with crossplattform support for MySQL5, PostgreSQL8 and others and FPC compatibility is directly depending on the ability to compile it with a compiler greater 2.0.2.

In the Moment we have the option to release next ZEOS recommending a nonworking 2.0.2 (Dataset Problems) or recommending a non working (memory leaks) other version.

And in the moment there exists none greater 2.0.2, which runs our testsuite without mem leaks.

As a RTL memory leak is a blocker for every serious application developer, all FPC users will benefit from a fix.

So the question to IMHO is simple:

1) We all have no time :-)
2) Someone changed something with the AS operator or memory management.
3) The same one will (hopefully) know that his change possibly made some side effects.

If that "someone" reads this, I hope I triggered him to say something like:

1) Ah - I know - I fix it.

OR

2) Ah - I know where the problem (sourcefilename) will be, but I have no time to do something about it.

In case 2 I hope he will say "Hey I have no time but the problem is serious just have a look at .... xxx.pp "

Then after SVN usage there will be the possibility to fix something, quicker then searching in the dark...

Thanks,

Helmut

---------------------------------------------------- Dipl.- Ing. Helmut Hartl
Head of Development
FirmOS Business Solutions GmbH

Show quoted text 30 lines
-----Ursprüngliche Nachricht----- Von: [mailto:fpc-devel- Im Auftrag von Joost van der Sluis Bereitgestellt: Mittwoch, 26. Juli 2006 12:44 Bereitgestellt in: fpc_devel Unterhaltung: AW: [fpc-devel] MemoryLeak with AS Operator Betreff: Re: AW: [fpc-devel] MemoryLeak with AS Operator > With 2.02 we have the problem that the TDataset has different behaviour > than in Delphi (Datetime). That's easily patchable. And idscussed in this list a few times. Just return a TDateTime in the GetFieldData. > No we are making production code with a self patched 2.02 release > (TDataset from 2.04) but that's no good solution. Why not? It's the only one. There are several other changes in 2.0.4 that you need to get ZEOS working properly. And as long ZEOS isn't released, you can safely build it against a fpc- version that isn't released. I guess that fpc 2.0.4 will be there long before the next ZEOS release. Joost _______________________________________________ fpc-devel maillist - http://lists.freepascal.org/mailman/listinfo/fpc-devel

Reply by email

Michael Van Canneyt
to Helmut Hartl
Helmut Hartl wrote 9 lines
Hello Joost, In the Moment we have the option to release next ZEOS recommending a nonworking 2.0.2 (Dataset Problems) or recommending a non working (memory leaks) other version. And in the moment there exists none greater 2.0.2, which runs our testsuite without mem leaks.

Have you tried the 2.0.4 release candidate ?
If there are no serieus bugs in it, this will be released in the next week(s).

It has all the fixes/additions of the main branch where TDataset is concerned.

Michael.

Reply by email

Joost van der Sluis
to Helmut Hartl: Maybe I should be a bit more informative: We (I) am the currently technical maintainer of…
Helmut Hartl wrote 5 lines
We (I) am the currently technical maintainer of ZEOS Database Library. We donate some of our work to the ZEOS DB Library. We are currently stabilizing it and using it in a carrier grade billing system for a VOIP Telco Provider.

I thought you were only working on ZEOS, and only answered to the database questions.

That mem-leak bug, do you have it's bug-number? And do you think it's serious enough to block the release of 2.0.4?

Joost

Reply by email

Luiz Americo Pereira Camara
to Michael Van Canneyt: Have you tried the 2.0.4 release candidate ? If there are no serieus bugs in it, this…
Michael Van Canneyt wrote 16 lines
On Wed, 26 Jul 2006, Helmut Hartl wrote: > Hello Joost, > > > In the Moment we have the option to release next ZEOS > recommending a nonworking 2.0.2 (Dataset Problems) or > recommending a non working (memory leaks) other version. > > And in the moment there exists none greater 2.0.2, which runs our > testsuite without mem leaks. > Have you tried the 2.0.4 release candidate ?

It seems that they tried. See item 11 of rc2 issues in Wiki/Issues page.

Luiz

Show quoted text 12 lines
If there are no serieus bugs in it, this will be released in the next week(s). It has all the fixes/additions of the main branch where TDataset is concerned. Michael. _______________________________________________ fpc-devel maillist - http://lists.freepascal.org/mailman/listinfo/fpc-devel

Reply by email