53099 - Mail Attachment get corrupted when memory is low

Status: VERIFIED WORKSFORME

(MailNews Core :: Composition, defect, P1)

Description

[Jean-Francois Ducarroz]

When I send a big attachment, it get corrupted. it's very easy to see the 
problem using a JPEG of about 75K. However, I don't see the problem with a 20K 
file.

step:
1) compose a message
2) either attach a jpeg file or insert it into the message body. The file should 
be at least 70K
3) send the message
4) retreive the message with either Mozilla or 4.x
5) ==> the image won't display correctly, the bottom of the image is missing!

Comment 1

[Jean-Francois Ducarroz]

change priority to P1 as it's a data loose.

Comment 2

[rhp (gone)]

Please attach the source from the message to see if this is a send side or 
rendering issue.

- rhp

Comment 3

[Jean-Francois Ducarroz]

it's not a rendering issue. I have tried with compressed file (.sit). Unstuffit 
is not able to read it when I sent a large file bug it's fine with a small one. 
I choose jpeg as sample because it's easier to see the problem. Anyway, I will 
attach two message, one sent with mozilla, the second one sent with 4.x...

Comment 4

[selmer (gone)]

Is this Mac only?  Can anyone else repro this?

Comment 5

[Jean-Francois Ducarroz]

I haven't tested it on Windows yet because my build isn't done!

Comment 6

[Jean-Francois Ducarroz]

Attachment: Image send from Mozilla which is corrupted

Comment 7

[Jean-Francois Ducarroz]

Attachment: Image send from Mozilla which is corrupted (again, better line feed)

Comment 8

[Jean-Francois Ducarroz]

Attachment: Image sent from 4.x which is good

Comment 9

[pmock]

fyi,
I could not reproduce this bug on win32, linux, and macos using todays build.  I 
tried using different files attachment including the Jeff's image. Jeff thinks 
it could be an issue of low memory on his system.  Jeff is investigating.  

Comment 10

[rhp (gone)]

Can I close this out?

- rhp

Comment 11

[Jean-Francois Ducarroz]

let me do more testing first...

Comment 12

[Jean-Francois Ducarroz]

Ok, the bug occurs only when I am low of memory on my Mac. Reassign this bug to 
myself for futur investigation. I don't think so we should hold PR3 for that.

Comment 13

[selmer (gone)]

nsbeta3- since you're futuring it.

Comment 14

[Jean-Francois Ducarroz]

Accepting

Comment 15

[scottputterman]

changing milestone to unknown.  It will get changed back when we figure out what
milestone to put this bug in.

Comment 16

[fenella]

Assign it to myself.

Comment 17

[fenella]

To Esther ..

Comment 18

[scottputterman]

moving to 0.9.7

Comment 19

[Jean-Francois Ducarroz]

I am running out of timw, it wont make it for 0.9.9. Moved to 1.0

Comment 20

[Jean-Francois Ducarroz]

Since this bug has been reported, the code has change a lot. I did the following
test with various memory setting to push Mozilla to the limite of a memFullErr
crash:

1) Open the browser
2) Drag&Drop a 750K image
3) Select Send Page
4) address the message to myself
5) send the message
6) Check the received image from another computer

The normal memory setting for Mozilla is 28672K. At 7000, we crash while trying
to open the image, at 7100K, we crash while typing the email address, at 7200K,
we crash during the send and at 7250K the message get sent and we crash during
the copy but the image is correctly received. All the crash occurs in various
location in Layout/XUL because we run of memory.

As I am not able anymore to reproduce the corrupted image: WFM.

Comment 21

[Trix Supremo]

verified wfm