After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 761384 - filters.xml duplicate entries
filters.xml duplicate entries
Status: RESOLVED DUPLICATE of bug 750560
Product: evolution
Classification: Applications
Component: Mailer
3.16.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2016-02-01 06:23 UTC by Conrad Steenberg
Modified: 2016-02-05 14:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Conrad Steenberg 2016-02-01 06:23:11 UTC
After upgrading to 3.16.5 in Ubuntu 15.04/Wily Evo started to experience periodic freezes for a few seconds at a time.

The file filters.xml was found to contain entries like these:
    <rule enabled="true" grouping="any" source="incoming">
      <title>Retail</title>
      <partset>
        <part name="sender">
          <value name="sender-type" type="option" value="contains"/>
          <value name="sender" type="string" allow-empty="true">
--->        <string>@MYHABIT.com</string>
--->         <string>@MYHABIT.com</string>
--->         <string>@MYHABIT.com</string>
            ....
          </value>
        </part>
        <part name="sender">
          <value name="sender-type" type="option" value="contains"/>
          <value name="sender" type="string" allow-empty="true">
--->         <string>store_news@amazon.com</string>
--->         <string>store_news@amazon.com</string>
--->         <string>store_news@amazon.com</string>
            ...
          </value>
        </part>

In some of the nodes the string tag was repeated up to 16384 times.

Slowdowns are gone after filtering out the duplicates in the file.
Comment 1 Milan Crha 2016-02-05 14:39:09 UTC
Thanks for a bug report. I suppose you didn't update straight to 3.16.5, because it already contains the fix for this. I od not think Ubuntu maintainers would patch 3.16.5 in some odd way here (like removing this particular fix).

*** This bug has been marked as a duplicate of bug 750560 ***