Report rendering and sql execution using up too much memory

Stimulsoft Reports.NET discussion
Post Reply
jing
Posts: 50
Joined: Fri Jan 26, 2007 12:47 am
Location: New Zealand

Report rendering and sql execution using up too much memory

Post by jing »

Hi,

We have manually created a database and a datasource from the report designer.
The query for the datasource is "Select * From f_table"

f_table is a big table with many fields and many rows (millions)
When we click the sql "run" button, the designer is using up nearly 800MB of memory and seizes the computer. This happens again when we preview the report..

Is there a way around this?

Is there a way to release the memory after an sql statement execution? (the designer seems to be accumulating the memory and does not release it after it's closed..)

Thanks
Vital
Posts: 1278
Joined: Fri Jun 09, 2006 4:04 am

Report rendering and sql execution using up too much memory

Post by Vital »

After report designer is closed you need dispose StiReport object and set reference to StiReport to null.
Thank you.
jing
Posts: 50
Joined: Fri Jan 26, 2007 12:47 am
Location: New Zealand

Report rendering and sql execution using up too much memory

Post by jing »

Thanks for your reply.
I was already doing that.

I guess it is not much of a problem providing the table does not have millions of records.

So is there no way to manually release the memory when the report designer is running? (say after preview/after running sql)

Thanks again
jing
Posts: 50
Joined: Fri Jan 26, 2007 12:47 am
Location: New Zealand

Report rendering and sql execution using up too much memory

Post by jing »

Any progress on this?

Is there a way to manually release the memory when the report designer is running? (Especially after preview and after running the sql query)

I have tried StiReport.ClearAllReportCache(), but it didn't make much difference...

Thanks very much
Edward
Posts: 2913
Joined: Fri Jun 09, 2006 4:02 am

Report rendering and sql execution using up too much memory

Post by Edward »

We've made some corrections in our code. Please download build from February, 15. It will be available today.

Thank you.
Post Reply