Closed
Bug 359537
Opened 19 years ago
Closed 19 years ago
TB crashes after replying to email or news posting and generates a talkback report.
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 356439
People
(Reporter: sunleyk, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Thunderbird version 3 alpha 1 (20061028)
When replying to either a newspost or regular email TB3 crashes and issues a talkback report upon closing via either the x or file exit or ctrl Q.
Reproducible: Always
Steps to Reproduce:
1.reply to an email or news posting
2.send the reply
3.or close the reply and not send
4.close TB
Actual Results:
TB opens Talkback and also windows tries to generate a crashed program message to send to Microsoft.
Comment 1•19 years ago
|
||
Yes, I'm seeing this also, but I think we need some refinement.
My feeling is that it happens only on html replies. Will gather talkback info
and watch closely when these crashes happen.
version 3 alpha 1 (20061102)
Comment 2•19 years ago
|
||
Please give the talkback id when reporting crashes.
I don't compose in html for newsgroups, only in text mode.
Here is the talkback id - TB25509753
Comment 4•19 years ago
|
||
---
Trigger Reason Access violation
Source File, Line No. N/A
Stack Trace
0x039bd763
nsTextServicesDocument::`scalar deleting destructor'
0x036e1c40
0xf9e0e908
---
Talkback didn't collect much of interest I'm afraid.
Just to confirm, this also happens on SM trunk too after posting a new news posting.
TB26625267Q - ignore the URL
Comment 6•19 years ago
|
||
This bug appears to be a duplicate of bug 356439 and/or bug 357861
(which may themselves be duplicates of each other).
Comment 7•19 years ago
|
||
This bug has already been reported as bug 356439. So I'm closing this as a duplicate.
Add yourself on the CC list there if you want to have feedback.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•