196013 - Crash opening the uploaded mail

Status: RESOLVED FIXED

(Core :: Layout, defect)

Description

[Marco Alberoni]

User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.3b) Gecko/20030211
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.3b) Gecko/20030211

If you open "File" -> "Open file" and select the mail I've uploaded, Mozilla
crashes.
The crash doesn't happen if you reduce at the minimum the html part, but if you
open the html part alone (extracting it from the mail), Mozilla works fine!

Reproducible: Always

Steps to Reproduce:
1.Open the uploaded file
2.
3.

Actual Results:  
Mozilla crashes

Expected Results:  
Mozilla has to show the mail

Here is the popuplog:

03-05-2003  11:04:30  SYS3175  PID 0078  TID 0001  Slot 00c4
C:\MOZILLA\BIN\MOZILLA.EXE
c0000005
1e940a30
P1=00000001  P2=0000001c  P3=XXXXXXXX  P4=XXXXXXXX  
EAX=00000014  EBX=1a9b8a14  ECX=00000008  EDX=0013c7c4
ESI=0000001c  EDI=0013c7c4  
DS=0053  DSACC=f0f3  DSLIM=ffffffff  
ES=0053  ESACC=f0f3  ESLIM=ffffffff  
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1e940a30  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:0013c788  SSACC=f0f3  SSLIM=ffffffff
EBP=0013c8d0  FLG=00212202

PMMERGE.DLL 0004:00110a30

Comment 1

[Marco Alberoni]

Attachment: The mail that crashes Mozilla

Comment 2

[Mike Kaply [:mkaply]]

Does this cash when you view it as an attachment in Bugzilla as well?

Can you please send me the whole Inbox? Just the mail isn't helping - send it to
mkaply at us.ibm.com

or send the offending mail to testing at kaply.com

thanks

Comment 3

[Marco Alberoni]

To crash Mozilla, I have only to left click on the attachment link
(http://bugzilla.mozilla.org/attachment.cgi?id=116291&action=view)... I think
the Inbox is not the issue.

Comment 4

[Mike Kaply [:mkaply]]

That might be an old bug that happened whenever you tried to save files

Could you try a current build?

Comment 5

[Hector Fabio Meza]

I left clicked on the link on comment #3 with build 2003030408 under win98se,
and it was displayed correctly, no crash.

Could be build or OS related.

Comment 6

[Mike Kaply [:mkaply]]

I'm not seeing this, even using the same build you were using.

My bet would be that this is the same type of font problems you were seeing in
the past, and your version of OS/2 crashes PMMERGE when you use bad font names.

The font tags in this document make no sense to me. Where did this mail come from?

Comment 7

[Mike Kaply [:mkaply]]

What is "Wingdings 2"?

Comment 8

[jhp (no longer active)]

I have a patch for this

Comment 9

[jhp (no longer active)]

Attachment: patch

Honor selection of codepage 65400 in system FONTMETRICS structure.

Comment 10

[Mike Kaply [:mkaply]]

Comment on attachment 116328 [details] [diff] [review]
patch

r=mkaply

Comment 11

[Jay Patel [:jay]]

Has anyone crashed with a Talkback enabled build?  It would be nice to know what
the stack signature and trace looks like for this crash for future reference. 

Comment 12

[Jay Patel [:jay]]

Whoops, didn't realize this was an OS/2 specific crash (we don't have Talkback
builds for OS/2).  Carry on. :-)

Comment 13

[Marco Alberoni]

Attachment: The html part of the mail previously uploaded

Opening this file, my Mozilla doesn't crash.

Comment 14

[Marco Alberoni]

Maybe it's my font problem, but if I extract the html part from from the mail,
create a .html file with it, and then open this file, I view it without problems.

Comment 15

[Mike Kaply [:mkaply]]

Your testcase is not the same. Put Windings 2 in quotes ("Wingdings 2") and it
will trap.

There are a few things that lead me to believe this is a font problem.

1. You are the same person that was trapping in PMMERGE using Wingdings and
Webdings :)

2. This web page specifically references Wingdings 2 which based on our prior
knowledge would trap on your system in PMMERGE because we don't handle it.

3. we are getting a broken image symbol from Mozilla which means it didn't even
try to display the image.

So based on that, I am checking in the font fix we have.

Either way, the fix we did is a good overall fix for this font problem, and
hopefully you won't see it again.