102314 - regression: cannot forward web pages

Status: VERIFIED WORKSFORME

(MailNews Core :: Composition, defect)

Description

[Bob Lord]

Build: 
Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4) Gecko/20010928 Netscape6/6.2 
WinME

When I try to send an email, I get an error dialog.

Comment 1

[Bob Lord]

Attachment: snapshot of error

Comment 2

[Bob Lord]

To reprodue: 
Visit a web page
Select either File/Send Page... or File/Send Link...
That's when I get the error.

Comment 3

[lchiang]

sheela - can you reproduce this?

Comment 4

[Sheela Ravindran]

I used 2001-09-28-05 branch build on win98. I was not able to reproduce this 
problem. I had the turbo switched off. I am not sure if this would cause any 
problems. 
Bob,
Is it while forwarding a page that you already received or when you are sending 
the page or link?  Is there a specific page that you are sending that can 
reproduce this problem all the time.  

Comment 5

[esther]

I tried this too and the few pages I sent to myself sent OK.  I then talked to
Bob on the phone.  He thinks turbo was on, he also mentioned that after exiting
the app and relaunching it worked.  He did say that he was able to reproduce
this a couple of times, but not now and that it appears to happen (as well as
other sluggish behavior) when he has left the app opened for long periods of
time (like
overnight).  This is on Windows ME, so I will have Ninoschka (she has Windows
ME) try this tonight.  Bob also thinks the content of the error might give us a
clue to why it's failing (note: the "T" on the second line of the error).

Comment 6

[Bob Lord]

I have not seen this bug for a while.  Feel free to resolve it.  I'll keep my
fingers crossed that the evil spirits have left my machine. ;-)

Comment 7

[Jean-Francois Ducarroz]

Per reporter comment, WFM

Comment 8

[Sheela Ravindran]

Verified as per reporter comments.  Reopen if this happens again. 

Comment 9

[Sheela Ravindran]

We have recent regression on send page and link broken on 2001-10-30-05 comm. 
trunk builds. (see bug # 107568)