Closed
Bug 274994
Opened 20 years ago
Closed 20 years ago
Visiting www.adaptec.com causes hard crash
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: pubgab, Assigned: bugzilla)
References
()
Details
(Keywords: crash)
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 Visiting http://www.adaptec.com causes hard crash with "buffer overrun" error 100% of the time. First occurred with several tabs, then tried only visiting the one page. After being prompted twice for cookies, firefox crashes. The cookie settings do not seem to get "set", so I am asked every time I go even though I tell firefox to use the option for all cookies coming from the site. This is true whether I choose to refuse or accept cookies. IE and Netscape do not seem to have issues with the site. No further information at this time. Reproducible: Always Steps to Reproduce: 1. Open firefox 2. Type "http://www.adaptec.com" 3. Answer any cookie questions in any manner. Actual Results: Error message stating something about a "buffer overrun". I did not write it down, and since I cannot run more than one instance of firefox at the same time, if I try to do it now, I will lose this post. Expected Results: See the page as normal.
Comment 2•20 years ago
|
||
pubgab@fariel.com: Are you able to reproduce with Firefox 1.0 final or with actual Firefox nightbuild? If so, please provide Talkback incident ID.
Severity: normal → critical
Summary: Visiting http://www.adaptec.com causes hard crash → Visiting www.adaptec.com causes hard crash
Comment 4•20 years ago
|
||
Well the reporter hasn't posted to this bug since December, nobody else has reported seeing this bug and it worksforme with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050524 Firefox/1.0+ ->WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•