Closed Bug 1443985 Opened 7 years ago Closed 6 years ago

Chinese or Japanese characters in Subject line cause hang when mail moved

Categories

(Thunderbird :: Untriaged, defect)

52 Branch
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: heisig, Unassigned)

Details

(Keywords: hang)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce: 1. click on mail with Chinese/Japanese characters (2-bit) in subject line and/or address 2a. drag that mail to another folder or 2b. drag that mail to the Desktop I am sending along a sample mail. Actual results: About 50% of the time, Thunderbird freezes, giving a (not responding) message. The program has to be restarted, after which the mail sometimes shows up as moved and sometimes not. Expected results: The file should have been moved or copied. Note: My version is 5.6.0, but you don't give the option above. Also I have the 32-bit installed because I couldn't find a 64-bit program for my Windows 10 OS.
What are your crash IDs? see https://support.mozilla.org/en-US/kb/mozilla-crash-reporter-tb#w_viewing-crash-reports (I don't crash using version 59.0b2 on windows 7 en-US locale)
Severity: normal → critical
Keywords: crash
There are NO crash reports. The message "Thunderbird not responding" appears at the top and just sits there until I close down and restart. Apparently, this undercuts the crash log that is supposed to be generates.
Attachment #8957038 - Attachment mime type: message/rfc822 → text/plain
I'm sure you mean TB 52.6, the current release version. TB 5.6.0 is certainly no longer supported, if it ever existed (since there were some jumps in numbers). I tried TB 52 and TB 60 Daily and saw no crash. The header are just "normal" RFC 2047 encoded headers which TB usually processes correctly: To: =?UTF-8?B?44OP44Kk44K444OD44Kv5YWI55Sf?= <heisig@nanzan-u.ac.jp> From: =?UTF-8?B?5Lit5p2R44CA576O5Luj6aaZ?= <55hamham@ic.nanzan-u.ac.jp> Subject: =?UTF-8?B?5p2x6KW/5a6X5pWZ56CU56m244Gu5YaK5pWw44Gr44Gk44GE44Gm?= Cc: =?UTF-8?B?6YeR5YWI55Sf77yIZ21haWwp?= <sechkim@gmail.com> Can you try to see whether some add-on interferes by disabling all add-ons, see Help menu.
Keywords: crashhang
Summary: Chinese or Japanese characters in Subject line cause crash when mail moved → Chinese or Japanese characters in Subject line cause hang when mail moved
Right you are. It is version 52.6.0 (32-bit) for Windows 10. It still happens intermittently, though less than before on subject lines or addresses with Chinese characters in them. If I figure about what is consistent about the "freezes," I will let you know.
J W, do you see this with *Windows'* in safe mode with networking enabled - win10 https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode ... and then still In Windows safe mode, start thunderbird in safe mode - https://support.mozilla.org/kb/safe-mode-thunderbird Rin, bogus, Have you ever seen this?
Flags: needinfo?(rokuyama)
Flags: needinfo?(heisig)
Flags: needinfo?(bogus)
I tried to reproduce this issue using several e-mails including the attached e-mail on my environment (Windows10 Pro 1709 build 16299.309 Japanese and Thunderbird 52.7.0(32-bit)). but I can't reproduce this issue.
Flags: needinfo?(bogus)
I also could not reproduce this problem on the following environments: - TB 60.0b1 (ja-JP-mac) on macOS 10.13.3 (Japanese) - TB 52.6.0 on NetBSD/amd64 8.99.14 (LC_CTYPE=ja_JP.UTF-8 and LANG and other LC_*=C)
Flags: needinfo?(rokuyama)
> 2a. drag that mail to another folder or > 2b. drag that mail to the Desktop These bits alone might have a duplicate bug. You are using version 52? Does problem reproduce with beta from http://www.mozilla.org/thunderbird/channel/ ?
Version: 5.0 → 52 Branch
I discovered this only happens on one of my computers. I do not want to uninstall and reinstall at the risk of loose all my folders in the current layout. Any other suggestions?
Flags: needinfo?(heisig)
Flags: needinfo?(heisig)
Reporter seems to be gone. Closing, but feel free to add more information
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(heisig)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: