1024984 - Thunderbird hangs when trying to save attachments

Status: RESOLVED DUPLICATE of bug 442908

(Thunderbird :: Untriaged, defect)

Description

[peer]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20140410211157

Steps to reproduce:

Version: 24.6.0

After the update to the current version, saving attachments doesn't work any more but instead crashes the application. It becomes completely unresponsive when trying to save any single attachment or using the save all button to save them all somewhere. Tried this with different mails, result is exactly reproduced.



Actual results:

Thunderbird became completely unresponsive. Files were not saved. The software is almost unusable in a professional context, because files received to be worked on are not available.
It even doesn't react to killing the process with Task-Manager sometimes.


Expected results:

Attachment(s) saved.
Thunderbird continues to react normally to user input.

Comment 1

[Wayne Mery (:wsmwk)]

(this isn't security)

we seem to be getting lots of these reports lately.
Does it happen if you have MS-WINDOWS started in safe mode?

Comment 2

[peer]

Ok, I fell in a trap which I should have known already. I ran into this before, but, well, forgot about it in the kind of panicky situation.

So what happened? I switched from working in my LAN to using the laptop off-LAN. On the LAN, before turning off the laptop, I accessed network folders which were not present in the roaming situation, so that caused the hang in TB after the wakeup of the computer.

After waiting several minutes (!), the "save file" dialog finally appeared and files can be saved normally.

Regarding the bug: Only if there is a possibility to programmatically catch this kind of situation without that long a delay (e.g. check if the networked "current" save-to-folder is available at all INSTEAD of just waiting for that long timeout delay to finish), that would improve the software such that I'd consider this bug as resolved.

Comment 3

[Wayne Mery (:wsmwk)]

thanks for the update