On Dec 4, 5:28 pm, Craig in Calgary <[email protected]> wrote:
> I have found that the longer I run FF non-stop, the slower it behaves.

I find the same thing, the upgrade to 3.05+ was supposed to stop the
memory hogging but it merely slowed it down a bit, it still
accumulates memory badly especially with long editing sessions.

I run procexp.exe all the time and watch the memory usage climb from
1.3Gb when I first start FF to 2.2Gb in a few hours.  Then I save
everything in TiddlyWiki kill FF and start again. FF has to many
lookaheads trying to outguess what you might do saving things you'll
never need,

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx AKA
procexp.exe

Morris

On Dec 4, 5:28 pm, Craig in Calgary <[email protected]> wrote:
> I have found that the longer I run FF non-stop, the slower it behaves.
> Lately I've been living in the TiddlyWiki space, reviewing adaptations
> and plugins, gathering notes for several university projects. I'll
> work in FF for 12-15 hours almost non-stop. At some point, I haven't
> tried to figure out the catalyst, FF begins to consume 40% or more CPU
> cycles. It won't release its stranglehold until I shut it down
> completely. Sometimes I have to reboot (Visa Home Edition).
>
> The size and complexity of your TiddlyWiki will affect the performance
> of FF somewhat. As my TiddlyWiki content loads grows, I'm beginning to
> considerhttp://jackparke.googlepages.com/jtw.html#ArchivePluginor
> something similar to try and reduce the load on FF.
>
> Good luck. Keep us posted if you learn anything.
>
> Craig

--

You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/tiddlywiki?hl=en.


Reply via email to