Closed
Bug 282880
Opened 21 years ago
Closed 21 years ago
sws.ncl.ac.uk views fine when logged in; if another url is loaded into the browser, browser will freeze and give critical error crash after about 5 seconds regardless of actions. perhaps a problem with transition from secure to non-secue browsing env...
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 282879
People
(Reporter: d.c.cosgrove, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
- Log into sws.ncl.ac.uk (webmail service) - Thawt security signed website
- Browse as much as you like (no problems with this website per se....)
- Navigate to ANY other website
- Browser gives critical error and shuts down all instances of the program
running (even other unrelated browser windows) after about 5-10 seconds of
displaying the new page (certinaly no navigation can occur without a crash)
- Happens every damn time. EVERY time.
Reproducible: Always
Steps to Reproduce:
1. Brose to and log in to sws.ncl.ac.uk: TRUST YOU HERE!!!: un = n2226089 pw
= ABCabc123123
2.browse it if you like: i doubt you need to.
3. navigate to another page, eg. ebay.co.uk/ google.co.uk: wait 5 seconds the
click a link or just breath or pick your nose or anything.
Actual Results:
critical error - crash of firefox.exe
Expected Results:
**** all... carried on as usual.
theme: qute 3
Comment 1•21 years ago
|
||
*** This bug has been marked as a duplicate of 282879 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Status: RESOLVED → VERIFIED
The original summary for this bug was longer than 255 characters, and so it was truncated when Bugzilla was upgraded. The original summary was:
sws.ncl.ac.uk views fine when logged in; if another url is loaded into the browser, browser will freeze and give critical error crash after about 5 seconds regardless of actions. perhaps a problem with transition from secure to non-secue browsing environment?
You need to log in
before you can comment on or make changes to this bug.
Description
•