Smalltalk › Frameworks & Tools › Seaside › Seaside General

[Pharo-Seaside] Autoload WWW-documents

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

marten

[Pharo-Seaside] Autoload WWW-documents

From my former VA problem I created a simple Component with the two
methods:

renderContentOn: html
html text: DateAndTime now printString.
html paragraph: 'Hello World from Seaside.'.
html paragraph: [
html text: 'To learn more about Seaside components follow the
link to the book: '.
html anchor
url:
'http://book.seaside.st/book/fundamentals/rendering-components';
with: 'Dynamic Web Development with Seaside'.
html text: '.' ].
1 to: 10000 do: [ :anIndex | html break. html anchor callback: [ ]
; with: 'www.heise.de' ].

and:

updateRoot: aHTMLRoot

super updateRoot: aHTMLRoot.
aHTMLRoot meta
responseHeaderName: 'refresh' ;
content: 1 greaseString

then I use a chrome with three tabs and after 2 hours the Pharo image
(the latest own downloadable) throws an out-of memory exception.
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

sebastianconcept@gmail.co

Re: [Pharo-Seaside] Autoload WWW-documents

We can talk forever of ways to consume resources and crash an image (or a linux kernel or a solaris one) and that would keep people distracted from doing stuff that matters.

I mean, it's okay to experiment and play, but came on man, give some real usage problems

sebastian

On Nov 12, 2010, at 2:02 PM, Marten Feldtmann wrote:

From my former VA problem I created a simple Component with the two methods:

renderContentOn: html
   html text: DateAndTime now printString.
   html paragraph: 'Hello World from Seaside.'.
   html paragraph: [
       html text: 'To learn more about Seaside components follow the link to the book: '.
       html anchor
           url: 'http://book.seaside.st/book/fundamentals/rendering-components';
           with: 'Dynamic Web Development with Seaside'.
       html text: '.' ].
   1 to: 10000 do: [ :anIndex | html break. html anchor callback: [ ] ; with: 'www.heise.de' ].

and:

updateRoot: aHTMLRoot

super updateRoot: aHTMLRoot.
aHTMLRoot meta
   responseHeaderName: 'refresh' ;
   content: 1 greaseString

then I use a chrome with three tabs and after 2 hours the Pharo image (the latest own downloadable) throws an out-of memory exception.
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

crux_op

Re: [Pharo-Seaside] Autoload WWW-documents

I'm curious.

Why doesn't garbage collection kick in?

I thought anytime the page is reloaded, it'd select a new callback id---thus pushing down the old ones in the registry. After a while, those old callbacks should be garbage collected and memory should be freed.

If not, then seaside could possibly crash for any long running session.

Johan Brichau-2

seaside sessions not cleared

In reply to this post by marten

Hi Marten,

I'm seeing the same thing happening.
The memory is only freed when I do a 'clear sessions' in the seaside tool.

This is strange because it seems the sessions should be cleared automatically in this case... (or I'm overlooking something too).

Johan

On 12 Nov 2010, at 17:02, Marten Feldtmann wrote:

> From my former VA problem I created a simple Component with the two methods:
>
> renderContentOn: html
> html text: DateAndTime now printString.
> html paragraph: 'Hello World from Seaside.'.
> html paragraph: [
> html text: 'To learn more about Seaside components follow the link to the book: '.
> html anchor
> url: 'http://book.seaside.st/book/fundamentals/rendering-components';
> with: 'Dynamic Web Development with Seaside'.
> html text: '.' ].
> 1 to: 10000 do: [ :anIndex | html break. html anchor callback: [ ] ; with: 'www.heise.de' ].
>
> and:
>
> updateRoot: aHTMLRoot
>
> super updateRoot: aHTMLRoot.
> aHTMLRoot meta
> responseHeaderName: 'refresh' ;
> content: 1 greaseString
>
> then I use a chrome with three tabs and after 2 hours the Pharo image (the latest own downloadable) throws an out-of memory exception.
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

marten

Re: seaside sessions not cleared

Hello Johan,

thanks for your reply, showing, that my problem shows "real usage problems".

And another word to Sebastian: showing how to crash a Linux kernel or
Solaris kernel gives us indication about errors we should be interested
in. Web application are server application, meaning, that they have to
face all possible server problems - even from people wanting to kill the
application.

Marten

Am 13.11.2010 20:57, schrieb Johan Brichau:
> Hi Marten,
>
> I'm seeing the same thing happening.
> The memory is only freed when I do a 'clear sessions' in the seaside tool.
>
> This is strange because it seems the sessions should be cleared automatically in this case... (or I'm overlooking something too).
>
> Johan
>

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside