Summary: | kmail hangs on some emails with adblock | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Christian Hesse <mail> |
Component: | general | Assignee: | Ivor Hewitt <ivor> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
this email is one of the mails having the problem
my adblock list |
Description
Christian Hesse
2005-06-28 19:37:52 UTC
Created attachment 11616 [details]
this email is one of the mails having the problem
There's no html in that example message. You're right, there's no thml in the example message. Nevertheless, I see the described behaviour with this message. KMail uses KHTML in all cases, even for non-HTML messages. It generates HTML from the plain text mail, for rendering purposes. Ah, completely misread original post as saying non-html mails do not have the problem. That sample opens instantly for me with AdBlock enabled. If you simply disable filtering is it still slow to open that mail for you? No, disabled filtering solves the problem as well. OK please attach your adblock filter list, or alternatively try to systematically reduce your filter list to determine if a specific filter is causing problems. Seems to be a proportional relation: The more url expressions I add the longer kmail hangs. OK please supply some details of your filter list. I have about 150 filters in my list and I don't see any noticeable slowdown with that mail message at all... and certainly not 10 seconds. Created attachment 11635 [details]
my adblock list
This is my adblock list that makes kmail hang for some seconds on some mails.
Reducing the list to the only entry "*/ads/*" kmail still hangs for half a
seconds (it's not long, but still noticable, especially when you click through
the mails with "Go to next unread message") on these mail.
Ok, isAdFiltered is getting passed a 2k "data:image/png;base64..." url from the HTMLTokenizer when that message is opened, combined with your filter set that kills QRegExpEngine. I'll add a url sanity check. Thanks. Ah, great news. ;) Can you please post a link to the patch? Thanks. Fantastic, this also fixes a bug which I have experienced with amaroK since we started using data: urls in the context browser. Thanks for the quick fix, ivor :-) |