Closed
Bug 224961
Opened 22 years ago
Closed 22 years ago
Crash (page fault) in SOFTOKN3.DLL when trying to send a mail.
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ppmozilla, Assigned: mscott)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20030925
Build Identifier: Thunderbird 0.4a 20031026 w GetAllMsgs extension
When trying to send a mail Thunderbird crashes in SOFTOKN3.DLL with a page fault.
For at least some mails (if not all where the abend occurs) this can be repeated.
I can sometimes go around this with "reediting" the mail at next try (copy/paste
a bit different etc.). It seems to happen when I copy paste something into the
mail.
Reproducible: Always
Steps to Reproduce:
1.Compose a new mail.
2.Paste something into it.
3.Try to send the mail.
Actual Results:
Page fault in SOFTOKN3.DLL.
Expected Results:
Sent the mail.
| Reporter | ||
Comment 1•22 years ago
|
||
An example.
| Reporter | ||
Comment 2•22 years ago
|
||
Exmaple 2 of a crash.
| Reporter | ||
Comment 3•22 years ago
|
||
With Thunderbird 0.4a M2 2003-11-05 I still get these crashes. At least one is
repeatable (haven't tried if the other is repeatable).
Seems to be related to if I have pasted at a part of the text into the compose
window. It doesn't help to edit the text afterwards.
Any interesting traces I can produce ?
| Reporter | ||
Comment 4•22 years ago
|
||
I *think* I have found the culprit. I used a file monitor and discovered that
the last file access before the abend was secmod.db.
I deleted secmod.db and restarted TB. So far, after several tests and restarts,
no abend.
Could it be that the format of secmod.db have changed between builds ? (Besides
common file corruption.)
| Assignee | ||
Comment 5•22 years ago
|
||
the format should not have changed but maybe something bad got written in there.
Please re-open if this happens again.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•