Subject | Re: [ib-support] URGENT: API memory leaks! |
---|---|
Author | Lev Assinovsky |
Post date | 2002-02-11T20:00:53Z |
Are you sure about isc_dsql_release? I didn't find it in documentation.
I use isc_dsql_free_statement(status_vec, stmt, DSQL_close) after last
fetch.
But memory still growing.
"Ann W. Harrison" wrote:
Lev Assinovsky Peterlink Web
Programmer St. Petersburg, Russia
Tel/Fax: +7 812 3275343 197022 ul.Chapigina 7�
E-mail: lev@...
[Non-text portions of this message have been removed]
I use isc_dsql_free_statement(status_vec, stmt, DSQL_close) after last
fetch.
But memory still growing.
"Ann W. Harrison" wrote:
> At 09:41 PM 2/11/2002 +0300, Lev Assinovsky wrote:--
> >I am not sure API memory management is clean.
> >I use about 150 different selects in non-stop client.
> >For few days the size of my application increased from 2 Megs to 5.
>
> What you haven't shown in your pseudo-code is any call
> that releases the request. Prepared requests are cached
> until they are released or the connection ends. The
> call
>
> which takes a status vector and
> a prepare statement handle as arguments is what you need.
>
> Regards,
>
> Ann
> www.ibphoenix.com
> We have answers.
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Lev Assinovsky Peterlink Web
Programmer St. Petersburg, Russia
Tel/Fax: +7 812 3275343 197022 ul.Chapigina 7�
E-mail: lev@...
[Non-text portions of this message have been removed]