Hi All guys, I have a A4-portait-style parent report (MBAXXX) with a fixed page header, fixed page footer and a subreport (MBA007) in the detail section. And this is the subreport (MBA007): As you can see, the subreport is all about a detail section and in the middle of the editor there's a subreport (let's call it MBA007_1) which contains a list with a variable number of elements. If I run the parent report (MBAXXX) and the result of the subreport (MBA007 due to MBA007_1 dimension) is smaller than the max dedicated detail band dimension (A4 minus page header and page footer dimension) I have no problem and I get a perfect one-page report (condition: MBA007_1 list contains 0-1 elements) If I run the report and the result of the subreport is big enough to "force" a second page, I get a perfect two-page report (condition: MBA007_1 list contains 3+ elements) The real problem is when the detail section of my parent report is closer to the max dedicated detail band dimension (A4 minus page header and page footer dimension) and the result should be a "perfect" one-page report (without empty space between detail and page footer sections) (condition: MBA007_1 list contains 2 elements) Running the parent report in this last condition I get a java.lang.OutOfMemoryError: Java heap space It seems like an infinite loop to me, and I can't understand how this could happen; the reason should be something about parent report calling subreport, but I'm not getting it! :-( In fact, If I run the subreport alone(MBA007) I get perfect results without problems in every condition (no matter how many elements MBA007_1 contains) EDIT: yesterday I had a similar issue with another subreport (same scenario) Instead of having a Java Heap Space Error, the parent report generated 996 pages (with the same content) of the same single expected page (running time about 15 min, when a "normal" run takes more ore less a few seconds) Thanks in advance, Fabio