Puntuado con 4 de 5 estrellas

por Dragodraki el Mar. 15, 2023 ·

The potential of this addon is enormous. Even in latest Thunderbird versions there is no function to schedule filters. So I decided to run a very outdated TB v.38 to use "Auto Filter Timer".

But: There is one very big disadvantage (exist in "Shedule Filters" too): No possibility setting filter to 1sec =0.017m (very helpful if local folders should get updated immeditately) without facing extreme CPU rise. This consumption continues increasing.

Possibly addon is lack of release the previous filter results - the shorter the time interval the faster the CPU rising.
Maybe this could be fixed someday. I know it has been a long time since then, but i think its worth it.

de DJ 'Cuppa' T (desarrollador) el Mar. 15, 2023 ·

I am still using a very old TB! You can safely use 52.9.1

The problem with short repetitions of filter runs is the fact it is done asynchronously on demand. This means that each run spawns a unique process which takes however long it takes... If a new run starts whilst the last one is still ongoing, then you will see twice the CPU activity in the same time-frame

The larger the mailbox, the longer the individual runs will take and the more likely they will overlap. This will definitely cause the escalating CPU rise you have witnessed. This will also cause filter runs to overlap their activity on the data itself, so if one run moves an email and the next run is expecting the same email there (because it was there a moment ago) there is a chance the filter system might be confused or go into a deadlock or other unpredictable behaviour!

Basically, you would need a very good reason to require immediate / continuous filter activity and this plugin is not a solution for that; TB itself would need that function built-in to avoid mad CPU hits