Hello Roland,
> > The problem still persists. I've managed to track it down to the
> > filter{js-annoyances} rule.
>
> Okay, that may be the cause for filter{js-annoyances} being disabled
> in all standard profiles (cautious, medium, and advanced). Simply use
> the default settings and everything is all right. If you think you
> need filter{js-annoyances} to be enabled, you have to live with the
> implications including maximum cpu load on some sites.
I think you are misunderstanding me: I do not only believe it causes
heavy CPU load, but that it is running in an endless loop which would be
definitely a bug. I have waited several minutes without the CPU load
going down again, and the website never gets delivered (an regexp
matching shouldn't be that expensive either...).
> As a work around, I suggest adding something like this to your
> user.action file:
>
> {-filter{js-annoyances}}
> www.memo.de
I did that once I figured out the cause :-)
Regards
Ben
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
