Closed Bug 288024 Opened 20 years ago Closed 19 years ago

Firefox crashes when selecting "Send Link..." from the "File" menu.

Categories

(Firefox :: Shell Integration, defect)

1.0 Branch
x86
Windows NT
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: bugzilla, Assigned: bugs)

References

()

Details

(Keywords: crash)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

While viewing
http://interviews.slashdot.org/article.pl?sid=04/10/20/1518217&tid=192&tid=214&tid=126&tid=11,
if I select "Send Link..." in the "File" menu, Firefox crashes with the
following message: "The instruction at "0x00480032" references memory at
"0x0032002d". The memory could not be "read".

Reproducible: Always

Steps to Reproduce:
1. Go to
http://interviews.slashdot.org/article.pl?sid=04/10/20/1518217&tid=192&tid=214&tid=126&tid=11
2. Select "Send Link..." in the "File" menu
Actual Results:  
Firefox crashed with the following message: "The instruction at "0x00480032"
references memory at "0x0032002d". The memory could not be "read".

Expected Results:  
A new message should have been openened in Outlook

For most pages, sending links works fine, but occasionally one will crop up such
as this one which consistently causes Firefox to crash while trying to send a
link. The OS is Windows NT 4.0 Workstation build 1381. The version of Outlook
involved is Outlook 2000 SR-1. This is a corporate workstation, so I can't try
this out with different versions...
Works for me

FF1.0.2 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.6)
Gecko/20050321 Firefox/1.0.2).

Link sent as normal.
(In reply to comment #1)
> Works for me
> 
> FF1.0.2 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.6)
> Gecko/20050321 Firefox/1.0.2).

I'm on Windows NT 4.0, maybe that's what makes the difference? Also, which email
client were you using?
Works for me as well. Using Windows XP with SP2 installed.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317
Firefox/1.0.2

It opens up Outlook Express v6 with the link in the body of the message.
Pepijn Schmitz: Could you provide Talkback incident ID for your crash?
Severity: major → critical
Keywords: crash
Version: unspecified → 1.0 Branch
WFM, alothough the actualy article you linked to no longer exists.  I used
another article to test.
(In reply to comment #4)
> Pepijn Schmitz: Could you provide Talkback incident ID for your crash?

No, 'cause Talkback doesn't work for me. I think it can't cope with a firewall
which uses NTLM authentication. Is there a way of saving the talkback report so
I can attach it or something like that?
(In reply to comment #5)
> WFM, alothough the actualy article you linked to no longer exists.  I used
> another article to test.

I just verified that the article does still exist. Like I said, most pages work
fine, it's very specific ones that FF has a problem with. Also I think the OS
matters, since I just tried sending the link using the same version of FF on a
Windows 98 SE system and Thunderbird as email client and it worked fine.
zip and attach %appdata%\talkback
As requested, here are the contents of my %APPDATA%\Talkback directory. There
seems to be data in there for multiple crashes. The directory you want to look
at is probably MozillaOrg/Firefox10/Win32/2005031717.
(In reply to comment #9)
> Created an attachment (id=179554) [edit]
> Contents of %APPDATA%\Talkback
> 
> As requested, here are the contents of my %APPDATA%\Talkback directory. There
> seems to be data in there for multiple crashes. The directory you want to look
> at is probably MozillaOrg/Firefox10/Win32/2005031717.

I examined the contents of the archive, and I could not find anything that
looked to be Talkback crash information in 2005031717.  I did however find .pak
files which contained what appeared to be crash information in 2004061423,
2004091322, and 2004110711.  I'm not really able to decipher the crash
information, as quite a bit of the contents of the .pak appear as boxes ([]) in
my text editor.  Perhaps someone else can decipher it.
tristor: the trick is to insert enough of talkback into the directories and copy
some files from the directories to other filenames, i did it once before, but
didn't quite document my setps. i'll deal with this later (hopefully not too
much later)
(In reply to comment #11)
> tristor: the trick is to insert enough of talkback into the directories and copy
> some files from the directories to other filenames, i did it once before, but
> didn't quite document my setps. i'll deal with this later (hopefully not too
> much later)

Sounds good, I would be interested to know how you do it once you have
remembered what you did, it sounds like it would be useful information to have
for the future.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: