hang when attempting to access a subpage from http://www.nikonusa.com/usa_home/home.jsp

RESOLVED EXPIRED

Status

()

Core
Plug-ins
--
critical
RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: james r, Assigned: Peter Lubczynski)

Tracking

({hang})

Trunk
x86
Windows 98
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624

i was attempting to access a subsidiary page for the Nikon Coolpix 3100 camera
from "http://www.nikonusa.com/usa_home/home.jsp" when mozilla 1.4 caused windows
98se to freeze.  the mouse and the keyboard were 'dead'.  i was able to recover
only by using the processor reset button on the front panel.  this caused
scandisk to check for disk errors when i restarted win98se

Reproducible: Always

Steps to Reproduce:
1.enter url: http://www.nikonusa.com/usa_home/home.jsp
2.find 'photography' area at the upper left of the page
3.click the underscored '3100' link found within the text


Actual Results:  
mozilla 1.4 froze. neither the keyboard nor the mouse could evoke a response
from win98se.   i had to press the 'processor reset' button on the system front
panel to recover.  a 'crash' report was not initiated when win98se  recovered.

Expected Results:  
accessed the page with further information on the coolpix 3100 camera.

no further information available -- no apparent 'crash' report activated.

Comment 1

15 years ago
do you also hang when going directly to URL
http://www.nikoncoolpix.com/3100/home.html ?
If so, which Flash plug-in version do you use (see about:plugins) ? Do you still
hang with Flash 6.0r79 ?
Keywords: hang

Updated

15 years ago
Summary: crash when attempting to access a subpage from http://www.nikonusa.com/usa_home/home.jsp → hang when attempting to access a subpage from http://www.nikonusa.com/usa_home/home.jsp
(Reporter)

Comment 2

15 years ago
I respond to "Comments From wolruf@free.fr  2003-08-23 20:53".  
i have no problem when i insert the
url"http://www.nikoncoolpix.com/3100/home.html" in the slot where the url
belongs; however, the same sort of crash ocurred when i clicked the link to
access the manual for the Coolpix 3100. i tried only that link. because of the
crash, i am not eager to try others from that url. i had not recorded the
precise version number in the file-name.  the install file is a .exe file of
size 12,263,120 and downloaded on 02jul03.

From "AboutPlugins" i do have the plug-in "Shockwave Flash, File name:
npswf32.dll, Shockwave Flash 6.0 r29" among others (I copied and pasted but
without some new-line and space characters) .  This plug-in was included in the
installation file i downloaded.  i am ignorant about ways to vary the plug-ins.
You asked: "Do you still hang with Flash 6.0r79 ? (copied and pasted from your
comment)". Do you think I should try 'flash 6.0 r79'?  If so, I will need more
education.

Comment 3

15 years ago
thanks for your comment, I think the LiveManual may be a different issue as it
involves Java. Let's save this for later. :)

2 things:
 - upgrade to latest Flash plug-in (6.0r79) by downloading the small (500KB)
installer here: http://www.macromedia.com/go/getflashplayer
 - if you still crash, submit the form (Netscape Feedback Agent) when crashing
and then post the Talkback ID associated to the crash here (via
"mozilla/bin/components/talkback.exe" ).
Assignee: general → peterlubczynski-bugs
Component: Browser-General → Plug-ins
QA Contact: general → bmartin

Comment 4

15 years ago
james, please comment within this bug report, Mozilla has the ability to search
NS4.x plug-ins when the plug-ins are not installed in Mozilla's own plugins/
directory. See http://plugindoc.mozdev.org/notes.html
What video card do you use and which driver version ? Upgrading to latest
version may also help here.
See comment 3 to upgrade Flash and submit Talkback data.
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.