*****Observed with linux and win32 05/14 trunk build***** After an IMAP attachment is opened on a browser window, selecting charset menu on that window causes a crash. Steps to reproduce: 1. Launch Mail. 2. Send yourself a mail with an attachment, it doesn't matter it's ASCII attachment or non-ASCII attachment. 3. After the mail is received, clicking on the attachment from the envelope to open it on the browser window. 4. On the browser windor for that attachment, select Edit | Character Encoding.. | <any encoding, like Wester (ISO-8859-1) The browser crashes.
There is a bug 72012 - IMAP: Charset menu on browser is not working when opening an attachment from envelope So this is not working but I have not seen it crashes.
Summary: Selecting charset menu on a window opened for an IMAP attachment causes crash → Selecting charset menu on a window opened for an IMAP attachment causes crash
Selecting View | Reload on that window causes crash as well. Will attach the call stack later when talkback server is accessible.
i have comments on my bug report ( bug # 80804) about changing encoding crash, if the stack is the same then it is a dup
Summary: Selecting charset menu on a window opened for an IMAP attachment causes crash → Reloading an IMAP attachment on browser window causes crash
Naoki, does selecting charset menu reload the attachment now? ( it didn't reload before, so we have bug 72012, right?)
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE
Verified as such.
Status: RESOLVED → VERIFIED
Reopen, because this is a generic problem which bug 80804 is non ASCII specific. I think bug 80804 is caused by this since charset menu change causes a reload.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
Below is the call stack: (It's different with the one for bug 80804. Please ignore my previous comments on 2001-05-14 16:16, I looked into a different incident): Call Stack: (Signature = docshell.dll + 0xa144 (0x6012a144) 0456c152) docshell.dll + 0xa144 (0x6012a144) docshell.dll + 0x9dfe (0x60129dfe) docshell.dll + 0xba59 (0x6012ba59) docshell.dll + 0x509b (0x6012509b) shistory.dll + 0x28ab (0x609528ab) shistory.dll + 0x255c (0x6095255c) xpcom.dll + 0x2c5c1 (0x60e7c5c1) xpc3250.dll + 0xfd7a (0x60b7fd7a) xpc3250.dll + 0x12e28 (0x60b82e28) js3250.dll + 0x181f0 (0x60c881f0) js3250.dll + 0x1cf68 (0x60c8cf68) js3250.dll + 0x1822e (0x60c8822e) js3250.dll + 0x184b5 (0x60c884b5) js3250.dll + 0x475a (0x60c7475a) jsdom.dll + 0x3184 (0x60543184) jsdom.dll + 0x15b14 (0x60555b14) gkcontent.dll + 0xb6aaa (0x60296aaa) gkcontent.dll + 0xb7aee (0x60297aee) gkcontent.dll + 0xe00d8 (0x602c00d8) gklayout.dll + 0x1fe0d (0x6032fe0d) gklayout.dll + 0x75591 (0x60385591) gklayout.dll + 0x736c1 (0x603836c1) gklayout.dll + 0x1fd83 (0x6032fd83) gklayout.dll + 0x1fbd0 (0x6032fbd0) gkview.dll + 0x143a (0x6045143a) gkview.dll + 0x13fb (0x604513fb) gkview.dll + 0x13fb (0x604513fb) gkview.dll + 0x13fb (0x604513fb) gkview.dll + 0x72b7 (0x604572b7) gkview.dll + 0x1d64 (0x60451d64) gkwidget.dll + 0x524a (0x60c2524a) gkwidget.dll + 0x7ec3 (0x60c27ec3) gkwidget.dll + 0x8292 (0x60c28292) gkwidget.dll + 0x56db (0x60c256db) USER32.dll + 0x1186 (0x77e41186)
Marking as nsbeta1. We should review this crasher before we release.
Retested with 05/21 trunk builds. It doesn't crash anymore on all the three platforms. Resolved it as wfm.
Status: REOPENED → RESOLVED
Last Resolved: 17 years ago → 17 years ago
Resolution: --- → WORKSFORME
Linux(2001-06-20-08 trunk) Mac (2001-06-20-08 trunk) Win32 (2001-06-20-06 trunk) Fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.