Thunderbird 115.12.2 and 115.13 freeze with FiltaQuilla 4.1 on Windows 11 / 21H2

[b00Ta]

I use Thunderbird 115.13.0 (115.12.2) + quickFilters 6.5.1 + Filta Quilla 4.0 (4.1) on Windows 11 21H2 Enterprise.

I have configured two IMAP accounts, the first one is active and is now hosted by Microsoft Outlook365 with our university domain, the second one is inactive now (it is old server and I keep it for an archive purposes).

With FiltaQuilla 4.0 everything I need works. But after update to 4.1 the Thunderbird within a while (it is random from several seconds to several minutes) starts freezing for many seconds and then run a little bit (like a second or two) and then freezes again. I am unable even to close it, I must kill it through task manager.

When it freeze whole GUI is unresponsive, the TB window cannot be moved at all. The left bottom status shows that it freeze in different states, sometimes is in "Looking for folder" state, in another freezing is in "Downloading headers..." or "Downloading messages...".

If it is running for a while after TB start and I run filters manually by [quickFiters] > [Run filters], it shows message that filters are running, like usually, and it takes some times, like usually, and then disappears, like usually, but nothing has been actually done.

The one thing I observed during freezing was when I look on Thunderbird processes by System Informer and looked at threads. The most CPU intensive thread points to some sound related call but no sound was produced.

I am now on FiltaQuilla 4.0 version with updates disabled as I need to work - I lost several hours by solving the problem (and needs to filter several tens of thousands of emails by plenty of rules after return from vacation).

[RealRaven2000]

can you check whether this is related to

• regular expression search in body
• multiple regular expression search terms in a single filter

there is some slightly changed code that uses the length of the message according to the same methods that Thunderbird uses. I will try to post a new version here that behaves closer the old way within TB115, but I am currently out of office (on annual leave until Aug 1st) so i cannot promise real deep patches within taht period of time. If I haven't come up with a solution by then, please ping me again here so I can prioritize this work.

[b00Ta]

I will try to investigate that on weekend, I have not so much free time during working days.

[RealRaven2000]

When testing, you can use debug mode and the additional settings you get when you right-click the debug mode checkbox for additional info in JS error console:

if there are operations related to reading / saving email body, you can activate

extensions.filtaquilla.debug.mimeBody = true

[cociweb]

Even on ubuntu 22.04 (v115.13.0/64 with the add-on version of 4.1)

Here is a standard log (without debug):

console.log: "FiltaQuilla [logTime init]\n"
JavaScript error: chrome://filtaquilla/content/filtaquilla-util.js, line 596: InternalError: allocation size overflow
console.log: "FiltaQuilla 15:14:53.440  [45534 ms]   \n"
JavaScript error: chrome://filtaquilla/content/filtaquilla-util.js, line 596: InternalError: allocation size overflow
console.log: "FiltaQuilla 15:22:1.163  [427723 ms]   \n"

Then after the crash: Exiting due to channel error.

Usually the crash is happening after console.log: "FiltaQuilla [logTime init]\n" even if the debug logging is activated.There is no additonal log even if debug (incl. mimeBody) logs are turned on

I've also catched in the TB crash report, that all of the available 16GB is allocated....

The root cause is unclear: it may or may not be regex-related. For testing purposes, I've disabled all rules containing regex. Now, TB does not crash. Again for testing purposes I've added a simple rule with BCC and the console returns the following: JavaScript error: chrome://filtaquilla/content/filtaquilla.js, line 1356: TypeError: headerParser.parseHeadersWithArray is not a function The rule does not apply... I'm not sure if it worked before or not, as it is a new rule for me.