Closed
Bug 5503
Opened 25 years ago
Closed 25 years ago
[PP]Application crashes when loading mail msg with vcard
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M5
People
(Reporter: fenella, Assigned: rhp)
Details
RE: win32 seamonkey build (1999-04-26-08)
Steps
1. Run apprunner.exe
2. Open mail application from Tasks|Messenger
3. Click on a mail message with vcard, apprunner application immediately.
Occurs on win_nt 4.0 consistently
RE: Linux (1999-04-26-08) build, when I load the same message with vcard, it
does not crash apprunner, but the message is displayed with the XML Parsing
error. (note: I have removed all the msf files prior to launching apprunner)
Updated•25 years ago
|
Assignee: phil → rhp
Target Milestone: M5
Comment 1•25 years ago
|
||
Reassign to rhp for M5
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•25 years ago
|
||
Hmmm...nothing changed here...this looks more like a problem with me getting
fed invalid data. Will investigate.
- rhp
Summary: Application crashes when loading mail msg with vcard → [PP]Application crashes when loading mail msg with vcard
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 3•25 years ago
|
||
I've just updated my tree and with the new XP-COM Vcard handlers, this seems to
be working fine for me on WinNT.
- rhp
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: WORKSFORME → FIXED
Due to rhp comments in e-mail:
"....I did checkin a bunch of stuff for content type handlers on Monday
and vCards fall into this boat..." I would like to mark this as Resolved/Fixed
for proper bug metrics. Doing now.
Severity: major → critical
Status: RESOLVED → VERIFIED
Hardware: PC → SGI
Verified in the April 29 build on all platforms. I tested it on Win32
(1999042908), Linux (1999042908), PPC (1999042910)
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•