You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by andyhot <an...@di.uoa.gr> on 2006/08/28 20:28:32 UTC
OutOfMemory in tapestry 4.0.2
Quoting from the user's list:
"I removed the @Body from the page and now the output seems to be
working fine.
The report is being outputed onfly as each component is rendered.
I guess the problem was really the buffer in the tag Body.
Thanks, Rodnei Couto"
This worries me a bit because i've introduced another buffering layer
(by rendering
the body of the @Shell in a nested writer) so that we can capture css
contributions
(similar to how we capture js contributions).
I'll try to do some performance & memory tests and report the results -
we might need
a smart way to reduce memory consumption esp. on nestedWriter.close()
I'm also not aware of @Body's history, but I was just wondering if
anyone had noticed
anything similar when Body started using buffering.
--
Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / J2EE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: OutOfMemory in tapestry 4.0.2
Posted by andyhot <an...@di.uoa.gr>.
devel - Fashion Content wrote:
> Is nestedWriter copying the content or maintaining a list to be merged?
copying the content
>
> I would like a copy of the @Shell you wrote if you dont mind :)
its in 4.1.1 as well as 2 new components... i'm currently updating the docs
>
> ----- Original Message ----- From: "andyhot" <an...@di.uoa.gr>
> To: <ta...@jakarta.apache.org>
> Sent: Monday, August 28, 2006 7:28 PM
> Subject: OutOfMemory in tapestry 4.0.2
>
>
>> Quoting from the user's list:
>> "I removed the @Body from the page and now the output seems to be
>> working fine.
>> The report is being outputed onfly as each component is rendered.
>> I guess the problem was really the buffer in the tag Body.
>> Thanks, Rodnei Couto"
>>
>> This worries me a bit because i've introduced another buffering layer
>> (by rendering
>> the body of the @Shell in a nested writer) so that we can capture css
>> contributions
>> (similar to how we capture js contributions).
>> I'll try to do some performance & memory tests and report the results -
>> we might need
>> a smart way to reduce memory consumption esp. on nestedWriter.close()
>>
>> I'm also not aware of @Body's history, but I was just wondering if
>> anyone had noticed
>> anything similar when Body started using buffering.
>>
>> --
>> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
>> Tapestry / Tacos developer
>> Open Source / J2EE Consulting
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / J2EE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: OutOfMemory in tapestry 4.0.2
Posted by devel - Fashion Content <de...@fashioncontent.com>.
Is nestedWriter copying the content or maintaining a list to be merged?
I would like a copy of the @Shell you wrote if you dont mind :)
----- Original Message -----
From: "andyhot" <an...@di.uoa.gr>
To: <ta...@jakarta.apache.org>
Sent: Monday, August 28, 2006 7:28 PM
Subject: OutOfMemory in tapestry 4.0.2
> Quoting from the user's list:
> "I removed the @Body from the page and now the output seems to be
> working fine.
> The report is being outputed onfly as each component is rendered.
> I guess the problem was really the buffer in the tag Body.
> Thanks, Rodnei Couto"
>
> This worries me a bit because i've introduced another buffering layer
> (by rendering
> the body of the @Shell in a nested writer) so that we can capture css
> contributions
> (similar to how we capture js contributions).
> I'll try to do some performance & memory tests and report the results -
> we might need
> a smart way to reduce memory consumption esp. on nestedWriter.close()
>
> I'm also not aware of @Body's history, but I was just wondering if
> anyone had noticed
> anything similar when Body started using buffering.
>
> --
> Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
> Tapestry / Tacos developer
> Open Source / J2EE Consulting
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org