crash when printing from amazon.com order history

RESOLVED EXPIRED

Status

()

Core
Printing: Output
--
critical
RESOLVED EXPIRED
14 years ago
12 years ago

People

(Reporter: Gero Mudersbach, Unassigned)

Tracking

({crash, top100})

Trunk
x86
Windows 2000
crash, top100
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [wfm?], URL)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031030
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6a) Gecko/20031030

When trying to print an order from amazon.com order history item page mozilla
crashes with the following error:
mozilla.exe - Application Error
The instruction at "0x00e1d1b4" referenced memory at "0x000000020". The memory
could not be "read". Click OK to terminate the program, click CANCEL to debug
the program.

This error does not occur when using Firebird.

Reproducible: Always

Steps to Reproduce:
1. Go to amazon.com, click "your account".
2. Select "complete order history by year" form the first combo-box, click go
3. Sign-in to your account (sorry, you need one to reproduce this)
4. Select an order and click "view order".
5. Print this, after clicking OK (print dialog) mozilla crashes with an
application error.

Actual Results:  
Mozilla closed with an application error dialog.

Expected Results:  
Print the webpage.

Updated

14 years ago
Severity: normal → critical
Keywords: crash

Comment 1

14 years ago
Cannot reproduce error, WFM
PC x86 Windows 2000 Mozilla 2003123008

Followed steps 1 - 5 exactly with my amazon.com account.
Page printed.
Printer: HP 5Si

Comment 2

14 years ago
My Epson printer isn't behaving at the moment, so I could only print to file. 
Printing the order history itself and an individual order WFM.
Mozilla/5.0 (Windows; U; Win98; en-US; rv:) Gecko/20040309

Reporter, does the problem still occur with a recent nightly build?  If so, then
please save a full copy of the page to your hard disk and either

(1) Zip all the files together and attach it to this bug.  You can replace any
personal or financial information with generic text or fake information. 

or better yet

(2) Try to create a working test case from the page, following the instructions
at  http://www.mozilla.org/newlayout/bugathon.html.  Then attach the testcase to
this bug.

Comment 3

14 years ago
Gero, please respond if you can still reproduce this using 1.6 final or 1.7b and
include the talkback ID if talkback (included in the installer buids) comes up
after the crash.

Updated

14 years ago
Keywords: top100
Whiteboard: [wfm?]
(Reporter)

Comment 4

14 years ago
I'm trying to get more information about the crash. Please be patient.

Comment 5

13 years ago
WFM, Mozilla 2004-12-16-06 trunk Linux.

Can anyone else reproduce the crash in a recent build?
If so, please save the page to disk and try to reduce it as much as possible
while still causing the crash and then attach the file here, using this link:
https://bugzilla.mozilla.org/attachment.cgi?bugid=228596&action=enter
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
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.