[tbnl-devel] Firefox

[Anthony F]

Perhaps "Leak" was too strong a word.  I'm not sure exactly what is going on 
yet, but here are the symptoms:

I start Apache, then TBNL.  I hit the test page with Firefox.  While 
watching the Process tab in Task Manager I follow a link.  Memory usage on 
the LispWorks process jumps anywhere from 2 to 5 megs.  Following any other 
links within the test app or refreshing the page causes the same until I hit 
LispWorks Personal's heap size limit and it dies.

I have yet to check if restarting Apache fixes the problem, but I will 
report on that later.  HOWEVER, I notice that even with IE a very small 
amount of memory seems to be leaking?  If you hit the Test app from IE, 
follow a link and/or repeatedly refresh I notice memory usage on the 
LispWorks process creep upwards ever so slowly.

Having said this, I have not actually done any real investigating yet (like 
I said, I'm a total newb)... so this may or may not be a result of expected 
behavior.

On a seperate note:  I don't really want to start a mod_lisp vs. other 
options war, but is anyone using a Lisp server (AllegroServer, TBNL's 
server, etc) back end in a production environment?  I was wondering about 
performance, security, other issues, etc.  Personally, I feel "safer" using 
Apache as it's battle hardened and fairly ubiquitous, but maybe those 
feelings are unfounded?  Any comments?

Thanks!

Anthony

----- Original Message ----- 
From: "Edi Weitz" <edi at agharta.de>
To: "Bob Hutchison" <hutch at recursive.ca>
Cc: <tbnl-devel at common-lisp.net>
Sent: Friday, September 30, 2005 6:26 AM
Subject: Re: [tbnl-devel] Firefox


> On Fri, 30 Sep 2005 09:01:01 -0400, Bob Hutchison <hutch at recursive.ca> 
> wrote:
>
>> And you know, thinking about it, I think I had to restart Apache
>> too.
>
> Yeah, that's one of the drawbacks of the mod_lisp backend - during
> development there are situations where you /must/ restart Apache or
> you have to cope with dangling connections.  I'm glad you contributed
> the stand-alone backend, that's what I'm using for development
> now... :)
>
> To the OP: Firefox/Win is my main browser and LispWorks is my main
> Lisp platform.  I'm not aware of any problems specific to these.  What
> exactly do you mean by "seemed to leak 3-4 megs per click?"
>
> As for the session stuff in the logs you might want to check with
> something like "Live HTTP Headers" to see what's going on.
>
> Cheers,
> Edi.
> _______________________________________________
> tbnl-devel site list
> tbnl-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/tbnl-devel
>