Closed Bug 263717 Opened 20 years ago Closed 19 years ago

Crashes when attempting to get and/or display the page that has the URL

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ocie2, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910

Browser crashes after I double-click on the URL (below) that is part of an
e-mail message displayed by Mozilla Mail & Newsgroups.  The browser loads and
evidently attempts to access and display the page specified by 

https://kphealthylifestyles.org/balance/e/e11.html?au=KPPLBASE&pid=308331

but Windows XP immediately displays an error dialog that "Mozilla needs to
close" and asks whether to send an error report to Microsoft.  Whether I agree
or cancel, both the browser AND the e-mail app are closed.  When I copy the URL
to the Windows clipboard, then paste it into the Internet Explorer 6.? location
bar data field, IE retrieves and displays the page without any evident problems.

By the way, I don't know whether that page will still exist after October 20. 
It is a log-in for a survey by Kaiser Permanente (HMO) to which they wanted me
to respond within 14 days of receiving the e-mail message, dated 6 October.


Reproducible: Always
Steps to Reproduce:
1.Paste the URL into the browser location field.
2.Press the <Enter> key on the keyboard.
3.

Actual Results:  
Windows XP displays a dialogue stating that it must close Mozilla.

Expected Results:  
Retrieved and displayed the website page.

I don't know what specific module was the origin of the crash, and I don't
recall seeing that data in the Windows XP dialogue.
When I tried again with the URL after posting the inital report, the Windows XP
dialog displayed the following "error signature":

          mozilla.exe
 AppVer   1.7.20040.25472
 ModName  nss3.dll
 ModVer   3.9.1.0
 Offset:  00033f60
Summary: Crashes when attempting to get and/or display the page that has the URL → Crashes when attempting to get and/or display the page that has the URL
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041010
Firefox/0.9.1+

May not be worth very much, but the URL given WFM with no unusual messages
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.3) Gecko/20040910

Do you use an adblocker extension, or a flash blocking extension?

JS Console shows some warnings.
They are checking for Flash and Quicktime support. I´ve got Flash installed, no
quicktime installed, and document.all disabled.
I don't crash in mozilla 1.7.3 or a recent 1.7.4 nightly. Note this is in NSS.
The server requests TLS 1.0 with TLS_RSA_WITH_RC4_128_MD5 if that helps. There
aren't that many crashes listed for NSS. Ocie, any thing unique how you have SSL
configured? use smart cards?
Mozilla\Help\About Plug-ins reports both Shockwave Flash 7.0 r19 and Quicktime
6.5.1 installed (along with Mozilla Default, Metastream 3, Adobe Reader 6.00,
Windows Media Player DLL, two Microsoft DRM, and several Java).  I don't use an
"adblocker" or a "flash blocking extension", but Spybot Search & Destroy is
running resident and blocking operation of some software intruders that might
display advertising -- in the context of the website that I've tried to access,
an attempt to display advertising would be rather odd.

All three of the SSL protocols are enabled, and a warning is displayed when
"loading a page that uses low-grade encryption".  I have never edited any
ciphers, and as far as I know, all settings on the SSL page are the defaults.  I
don't use "smart cards" (dunno what they are <sigh>).
After posting replies to the three people who posted additional comments, just
out of idle curiousity I accessed the e-mail message that contains the hyperlink
to the website page and double-clicked on it as before.  The page was evidently
 retrieved and displayed without any problem, and I've repeated that at least
twice.  I also used the browser feature to "clear the cache" and repeated the
maneuver with the same outcome -- which leaves me wondering what has changed
since I submitted this bug report.  (Granted, I rebooted the OS since, so maybe
the three failures last night were caused by a problem with Windows XP??  Next
time, I guess I should restart the OS before reporting a bug here!)
WFM = Works for me

which implies that there is no suggestion that anyone has fixed the bug, 
but that there are no further pointers or leads to investigate. Many WFM 
bugs are not associated with errors or defects in Mozilla, and checking 
platforms and products other than the one reported on can help in locating 
any problem.

In this case, my report may not have worth very much, because there were some
indications already that this problem was specific to Windows.

Sometimes Mozilla will emit error messages to STDERR and will nearly always
notify when Flash or Java is started. 

The bug documentation is at http://www.mozilla.org/get-involved.html .

Bug reports are important because they are the raw material for world class
software.

I don't personally recommend rebooting software, but then I don't run 
an OS that spontaneously decays
Product: Browser → Seamonkey
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
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
resolving WFM according to reporter's comment #6
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.