toggle visibility causes out of memory error

[SQLWilts]

Hi,
Running visual studio 2005 on win XP with 2GB ram.

I have a SSRS 2005 report that runs just fine when all fields are expanded. All the groups are there, and all is right with the world.

I now right click the detail line, edit group, choose visibility, select "visibility can be toggled by another report item", leaving "initial visibility" as "Visible" and again, the report runs in about 10 seconds and works fine.

I go back into the report and choose visibility and set the initial visibility to "hidden" and the report runs for a little longer (not much) but fails with a "system.outofmemoryexception" error. this happens when the "devenv.exe" process hits about 840MB.

Has anyone found a work around to this issue? The report is returning about 28,000 records of about 23 fields, so it isn't as if it is a massive data set that it is working with.

Any ideas would be appreciated

 

[AlexCuse]

Just a guess, but it sounds like you have a cyclic dependency in your visibility settings. Something like "for X to be visible, Y must be clicked" and "for Y to be visible, X must be clicked". When processing the report, the computer basically ends up in an infinite loop and exhausts the memory allocated to SSRS.

If you look at the settings in your groups' visibility I bet you will find something out of sequence, or otherwise amiss.

Hope this helps,

Alex

[small]----signature below----[/small]
Majority rule don't work in mental institutions

My Crummy Web Page

 

[SQLWilts]

Alex,

Thanks for replying.

Nope, I had already checked for all that. I was given a copy of the offending .rdl and stripped it down so that there is only one group, visibility is set at the group level, dependant on one field in the group header, that the group is grouped on (phew!). nothing else. I took out any aggregation done in the report and made the SQL engine do that (even the data set calls a proc!). The only thing left in the report is the grouping and the visibility.

It's all a little dissapointing really....

 

[AlexCuse]

Is it doing a lot of complex calculations?

Anything of interest in the code window / references (possibly undisposed resources and such)?

Does it open correctly if you deploy it to the server?

We'll need to know more about your report in order to help.

Good luck,

Alex

[small]----signature below----[/small]
Majority rule don't work in mental institutions

My Crummy Web Page

 

[SQLWilts]

Hi Alex,

Nothing in the code window, no calculations in the report at all!

Very strange.

One group only in the report now.

If the group is set as initial visibility "visible", it works fine. I hide it (no conditions attached - just initial visibility "hidden") and it fails with "out of memory" error. I can watch the memory counter rising in task manager. There are a lot (hundreds) of small groups though...

It may be a case of writing a drill through report, but that kind of spoils the effect

 

[AlexCuse]

Hm, that is curious. What effect are you going for?

[small]----signature below----[/small]
Majority rule don't work in mental institutions

My Crummy Web Page

 

[SQLWilts]

A list of all customers who ordered something this year/period/month (whatever) with pluses next to them so that the user can drill into each customer to see their orders.

Even the sorting is done in the proc.

Incredibly basic stuff really - considering some of the more complex matrices I have built and run with little problems!