While the parameter: mail.compose.attachment_reminder_keywords is handy, there needs to be a threshold to message size (or at least message type) whereby it stops looking for the keywords. I recently had to copy and paste a spam containing a virus (base64 encoded) into a message body (because some idiot abuse departments don't accept attachments) and TB tried to parse all 3MB of base64 virus. This took 7 minutes. If the message body is longer than say 100KB, it's likely that there are no attachments missing and this can be skipped. Similarly, there's no point in parsing a base64 block... skip it and go on to the next part of the message.
Can we get some movement on this? Do I need to do any additional follow-up or is this report complete?
(In reply to Philip Prindeville from comment #1) > Can we get some movement on this? see 1.2 of https://bugzilla.mozilla.org/page.cgi?id=etiquette.html plus so many bugs, too few developers means this isn't likely to get fixed soon, if ever, unless someone who cares about this specific issue drops by and has the skills and time to fix it. > Do I need to do any additional follow-up or is this report complete? it is complete workaround: one can avoid the N minutes delay by explicitly adding a small attachment to the message, before pasting the large message
Severity: enhancement → minor
Summary: Searching for 'attachment' et all on very large messages locks up TB for long periods → Searching for 'attachment' et al on very large messages locks up TB for long periods. Sanity check when using mail.compose.attachment_reminder_keywords
You need to log in before you can comment on or make changes to this bug.