Fatal Error causing all copies of Firefox to close

RESOLVED EXPIRED

Status

()

Firefox
General
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: Standard Interface, Assigned: Ben Goodger (use ben at mozilla dot org for email))

Tracking

1.0 Branch
x86
Windows 98
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

In Firefox version 1.0

this link http://www.picsurfer.com/m/xxxsalsa-080/6a.htm

causes this FATAL error everytime

FIREFOX caused an invalid page fault in
module KERNEL32.DLL at 017f:bff7a388.
Registers:
EAX=000a000d CS=017f EIP=bff7a388 EFLGS=00010206
EBX=00000f14 SS=0187 ESP=00c9b1e8 EBP=00c9b20c
ECX=007d000a DS=0187 ESI=030c7a64 FS=4ab7
EDX=c172f360 ES=0187 EDI=000cf124 GS=0000
Bytes at CS:EIP:
89 41 08 8b 56 04 8b 46 08 89 50 04 8d 04 1e 50 
Stack dump:
000cf124 00000000 030c000c 030c0000 030c7a64 
00000000 00000000 00003197 000030c8 00c9b234 
bff7a550 030c0000 030c7a64 00000f14 00000000 
00000f04 

This error also existed in Firefox 0.8

Can it be fixed?

P.S. The Link works fine in IE and in Mozilla.




Reproducible: Always
Steps to Reproduce:
1. see details
2.
3.

Actual Results:  
Fatal Error

Expected Results:  
Played Movie

see details
-> General
Component: Product Site → General
WFM, Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050408
Firefox/1.0+

Reporter, do you see this reported Problem with a current Build/Release (Firefox
1.0.2) ?
Version: unspecified → 1.0 Branch

Comment 3

13 years ago
FIREFOX caused an exception 03H in module JPINSCP.DLL at 016f:6d422bc1.
Registers:
EAX=6d422bc0 CS=016f EIP=6d422bc1 EFLGS=00000206
EBX=6d420000 SS=0177 ESP=00c9eed0 EBP=00c9ef00
ECX=00000080 DS=0177 ESI=6d42f004 FS=8a5f
EDX=00de5a5c ES=0177 EDI=00000000 GS=0000
Bytes at CS:EIP:
2b 42 6d 0e 00 00 00 07 00 00 00 05 00 00 c0 00 
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: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.