1869226 - Closing TB with open message tabs, then opening TB, leads to tabs which error rather than load with "IMAP not registered protocol"

Status: RESOLVED DUPLICATE of bug 1846054

(Thunderbird :: Toolbars and Tabs, defect)

Description

[Luke T. (AU)]

Attachment: Screenshot showing multiple tabs, 1 of them open, showing the error post-restart

Steps to reproduce:

Closed Thunderbird when there were open email viewer tabs. Then re-opened Thunderbird which led to those previously-OK tabs to not be OK.

Actual results:

The tabs opened after application restart with "IMAP not a registered protocol" error instead for each one that was open. Implying potentially they are trying to open before the back-end pre-requisite works including registrations were complete?

Expected results:

Tabs re-opened with the email content for each respective tab - ie. no error.

Comment 1

[Luke T. (AU)]

Thanks. This may be improved/resolved in v115.5.2 even though I can't quickly see a matching fix:

https://www.thunderbird.net/en-US/thunderbird/115.5.2/releasenotes/

Will keep an eye on it now there's a new patch release.

Comment 2

[Luke T. (AU)]

It has happened again since the patch release.

Comment 3

[gene smith]

Before restart, was there a PDF open and displayed in the tab? If so, what is its size and what is the containing email's full size. You can tell the email size by enabling a "size" column in the list of emails pane. Not sure how to know the pdf size but obviously < the email size.
To show a PDF within TB you have to set "File and Attachment" for PDF to "Preview in TB". Otherwise it asks you to show it in an external viewer. So you probably have that set.
Are you using offline store or just keeping everything on the server?
I don't use offline store and just opened a huge email 100M with a huge PDF and opened the PDF in a tab. Then when I restarted, the PDF was retrieved from disk cache and displayed in the tab properly, unlike what you seem to be showing in the screenshot.
FWIW, if you are not using offline store and if your message size is greater than about 50M, you can increase the max size of the disk cache entries by setting browser.cache.disk.max_entry_size to -1 and restart TB. But this won't have an effect if the folder containing the huge message is using offline store (mbox or maildir).

Comment 4

[gene smith]

Well I am seeing a problem with big PDFs in tabs not coming back after a restart. I'm not seeing anything about "imap not registered". What I see is that the loading progress indicator at the top gets about 1/3 of the way and just stops and the tab remains empty. I had 3 tabs with the large PDF open with 2 blank and one showing. Then I shut down newest daily and started old 110. That was the last version I tested this with and had it was working fine. When I started 110, all the tabs loaded as they should. I also added more PDF tabs with 110 and shutdown and restarted and they all came back fine. (These are fairly huge 30M PDF in each tab.) Since I haven't made any changes in imap code that handles this since 110, it must be the the other UI changes affecting this. Also with new daily (and I assume 115) that loading the huge messages from cache is more sluggish but is still reliable (until after a restart when re-loading tabs from a URL fetching a part).

Reporter Luke T: Can you attach or email me a saved email with attachments that have the problem you are seeing?