47854 - Send fails, Save as draft fails

Status: VERIFIED WORKSFORME

(MailNews Core :: Composition, defect, P3)

Description

[Ben Bucksch (:BenB)]

Warning: Bad bug report.

I cannot reproduce consistently, but often when I use Mozilla to compose long
(HTML) mails, the send operation seems to fail without error, and the Send/Save
commands get enabled again. I then pressed Save(AsDraft), this operation fail,
too, but this time, the Send/Save commands stayed disabled. I also had high CPU
usage. *IIRC*, the Send operation finally succeeded (after some minutes), but I
got a notice that the Sent copy failed.

Comment 1

[Ben Bucksch (:BenB)]

BTW: Running Draft and Sent on UW-IMAP. Well possible that 4.x ran at the same
time, don't remember.

Comment 2

[Ben Bucksch (:BenB)]

I run into this bug for pretty much every longer msg I compose. It makes Mozilla
Mailnews unusable for me (not that I would use it much anyway :) ). DOGFOOD. I
know, I have no reliable reproduction. What can I do to help to create one?

4.x didn't run at all the last times, so this is not the reason.

Because I know of this bug, I occasionally hit Save(AsDraft) sometimes, but
usually the one after 10 mins or so of composing fails, leaving Send/Save UI
disabled without carrying out the save operation.

Comment 3

[Ben Bucksch (:BenB)]

Moving to component Composition and ccing ducarroz, because this bug appears for
both SaveAsDraft and Send.

Comment 4

[leger]

since intermittent, putting on [dogfood-] and adding nsbeta3 nominee keyword.

Comment 5

[lchiang]

per mail triage, correcting status whiteboard to "need repro" since that's how 
we'll track bugs needing QA to reproduce.

Is this when the server was unavailable?  Perhaps we can try to reproduce using 
Parp (Netscape internal test server we control) by shutting down the server.

Comment 6

[Ben Bucksch (:BenB)]

> Is this when the server was unavailable?

Not that I know of.

Comment 7

[Ben Bucksch (:BenB)]

Raising severity to critical, since this is data loss (if you don't count
Debug|OutputHTML feats).

Comment 8

[Scott MacGregor]

I haven't been able to reproduce this. We need to somehow come up with a test
case or something to catch it in the act. 

Comment 9

[Karen Huang]

> I also had high CPU usage

Ben, is this bug originally reported from Linux platform? And is it occurring on 
all the platforms?

Comment 10

[Ben Bucksch (:BenB)]

> > I also had high CPU usage

I'm not sure this happens in all cases.

> Ben, is this bug originally reported from Linux platform?

Yes.

> And is it occurring on all the platforms?

Dunno.

Comment 11

[Karen Huang]

By using 08-17-08-M18 Linux commercial build:
I couldn't reproduce this problem on UW IMAP mail account for both migrated 
profile & new profile. 
I did try on the long HTML messages for both send & save as draft scenarios, but 
I still couldn't reproduce this problem.
Ben, can you try on the latest Linux build again since we had fix for CPU usage 
around beginning of Aug. I am wondering to know whether this is still an issue 
for the current build...updating status whiteboard [need help for reproduce].

Comment 12

[lchiang]

- per mail triage until we get a reproducible case and we'll look at this again.

Comment 13

[Eugene Savitsky]

2000090308 win2000 saw this yesterday.

Comment 14

[lchiang]

ezh: do you have a reproducible set of steps that you can help us with?

Comment 15

[Eugene Savitsky]

Not yet, but I'm using mozilla's newsreader for second time today.

Comment 16

[Ben Bucksch (:BenB)]

eugene, when the error occured, did you spend a lot of time (say, > 20mins) to
compose the msg? I shortly tried to reproduce the bug by recreating the same
circumstances and doing the same actions (but didn't spend so much time), but I
couldn't reproduce.
Maybe, I should eat more dogfood to get a clue, but I'm not keen to lose my
work... :(

Comment 17

[Ben Bucksch (:BenB)]

What relevant logging mechanisms do we have (other than the IMAP log)? I might
take the risk, if I could be reasonably sure to get a clue about the cause, when
the bug occurs again.

Comment 18

[Eugene Savitsky]

Ben, I also thought about the time I composed those message. It was about 15-20 
minutes...

So maybe this is the problem?

Comment 19

[hirata masakazu]

I have a very reproducible case.
You have to have Mail/News window closed and have only the message compose
window opened by New Message from pull-down menu, or maybe from mailto tag.
Then Save simply fails.  This is really bad.
2000101608 Mac

Comment 20

[hirata masakazu]

Actually, the only time I can get the message seved to Draft is when a message
compose window is opened by clicking the New Msg in Mail/News. It does not
matter how long you have spent.
BTW, my case is POP.  Please file a new bug if this bug is not about POP.

Comment 21

[Scott MacGregor]

triaging.

Comment 22

[Ben Bucksch (:BenB)]

hirata,
there was a bug about SaveAsDraft failing recently. Please grab the latest
*trunk* (not MN6) nightly build and retest. It works for me. If you still see
the bug, please file a new one, as the bug you see doesn't seems to be exactly
the same as this one.

Comment 23

[Ben Bucksch (:BenB)]

(stepped over 1 of mscott's changes (QA).)

Comment 24

[Jean-Francois Ducarroz]

Per Ben last comment, works for me. Please reopen if you still see this problem
with a recent build.

Comment 25

[Ben Bucksch (:BenB)]

Will do.