Closed
Bug 105120
Opened 23 years ago
Closed 23 years ago
Crash viewing source of a '1969' bogus message.
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
People
(Reporter: stephend, Assigned: sspitzer)
Details
Attachments
(2 files)
Build ID: 2001-10-16, 0.9.4 branch.
Summary: Crash viewing source of a '1969' bogus message.
Steps to reproduce: Put this in a local folder, and try to view source.
Actual Results: We crash.
Expected Results: No crash.
|
Reporter | |
Comment 1•23 years ago
|
||
|
|
Reporter | |
Comment 2•23 years ago
|
||
|
|
Reporter | |
Comment 3•23 years ago
|
||
I had hoped to attach the bogus message, but it's 0 bytes, so worthless, indeed.
This bug wouldn't exist and depends on us creating the bogus message in the 1st
place. To create the bogus message, I did a combination of copying the POP3
message in my inbox to trash, then attempted to move it to the trash. When I
switched folders and came back to the inbox, I saw the 1969 message.
i think this one is bogus... how can a 0 byte message possibly land in the
inbox?
|
|
Reporter | |
Comment 6•23 years ago
|
||
r.k.aa, who knows how the corruption got there. I did my best to explain the
scenario, but the main point is that there might need to be some code to check
if we have some bogus portions in a message before viewing source (so at least
we don't crash). The message itself being bogus is another, already filed bug.
|
|
Reporter | |
Comment 8•23 years ago
|
||
Indeed.
*** This bug has been marked as a duplicate of 78785 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
|
||
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•