Report Hang and Memory Spike
-
- Posts: 42
- Joined: Thu May 05, 2011 7:12 pm
Report Hang and Memory Spike
If a pages width is smaller than a chart the report hangs when running and the memory spikes until the IIS is reset. This is not good as it cause the whole website to hang.
Report Hang and Memory Spike
Hello,
Which version and build of Stimulsoft Reports do you use?
We couldn't reproduce this bug.
Can you please send us a sample report template with data, which reproduces the issue?
Thank you.
Which version and build of Stimulsoft Reports do you use?
We couldn't reproduce this bug.
Can you please send us a sample report template with data, which reproduces the issue?
Thank you.
-
- Posts: 42
- Joined: Thu May 05, 2011 7:12 pm
Report Hang and Memory Spike
Hello,
The attached report will produce the hanging issue with out the data connection.
Thanks
The attached report will produce the hanging issue with out the data connection.
Thanks
- Attachments
-
- 1053.ReportError.mrt
- (20.46 KiB) Downloaded 357 times
Report Hang and Memory Spike
Hello,
Unfortunately, the Chart component is not breakable.
So please do not make the chart size larger than the page size.
Thank you.
Unfortunately, the Chart component is not breakable.
So please do not make the chart size larger than the page size.
Thank you.
-
- Posts: 251
- Joined: Fri Feb 04, 2011 11:46 am
- Location: San Diego, CA
Report Hang and Memory Spike
Sorry, I do not understand your response.
Yes making the chart size fixes the CPU hang ... but it demonstrates a CPU and memory spike bug in the report engine. It is very easy for an end user to create a report that causes this CPU and memory spike. The report designer is used by end users ... so we have no control over how they create reports. But an end user should not be able to create a report that causes a CPU and memory spike that requires an IIS restart or server restart to recover from. We have accidentally created reports that cause a CPU hang 6 times already. Each time it required a server reboot or IIS restart. These are production servers so this is impacting many users.
Can the report engine catch scenarios like this instead of requiring a reboot of the server?
Thanks,
Jay
Yes making the chart size fixes the CPU hang ... but it demonstrates a CPU and memory spike bug in the report engine. It is very easy for an end user to create a report that causes this CPU and memory spike. The report designer is used by end users ... so we have no control over how they create reports. But an end user should not be able to create a report that causes a CPU and memory spike that requires an IIS restart or server restart to recover from. We have accidentally created reports that cause a CPU hang 6 times already. Each time it required a server reboot or IIS restart. These are production servers so this is impacting many users.
Can the report engine catch scenarios like this instead of requiring a reboot of the server?
Thanks,
Jay
Report Hang and Memory Spike
Hello,
We made some improvements in that direction.
Please check the next prerelease build from 8-Jun-2011 when it will be available and let us know about the result.
Thank you.
We made some improvements in that direction.
Please check the next prerelease build from 8-Jun-2011 when it will be available and let us know about the result.
Thank you.