Closed
Bug 286974
Opened 20 years ago
Closed 20 years ago
Loading this URL causes a memory "read" or "write" failure
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: Hamish.MacEwan, Assigned: bugzilla)
References
()
Details
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Loading the above URL causes "Memory read error" Restarting Firefox results in it consuming all available processor time but remaining non-responsive. Reboot or restart clears this loop condition. Reproducible: Always Steps to Reproduce: 1. Load the URL Actual Results: As above Expected Results: Load and render the page.
Comment 1•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050319 Firefox/1.0+ WFM
Comment 2•20 years ago
|
||
WFM: 1.0.1 and latest trunk build on XP
| Reporter | ||
Comment 3•20 years ago
|
||
| Reporter | ||
Comment 4•20 years ago
|
||
1. The error is repeatable, but the values ("instruction", "memory" and
direction ("read" or "write") change each time.
2. Reboot is essential to clear what ever corruption leads to the loop (all
available CPU consumed).Summary: Loading this URL causes a memory read failure → Loading this URL causes a memory "read" or "write" failure
| Reporter | ||
Comment 5•20 years ago
|
||
The orginal URL (which I had trouble with) redirects to: http://computerworld.co.nz/news.nsf/NL/6A53B1A107AF13A6CC256FCA001AA96C On that URL, Firefox crashes without comment. Hamish.
Comment 6•20 years ago
|
||
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050319 Firefox/1.0+
| Reporter | ||
Comment 7•20 years ago
|
||
Comment 8•20 years ago
|
||
wfm with Mozilla/5.0 (Windows; U; Windows NT 5.2; de-DE; rv:1.8b2) Gecko/20050317 (Mozilla cvs trunk) and FF1.0.1 Reporter: Sorry but we are unable to reproduce the problem. Run FF1.0.1 in the safemode (without extensions) and if you still crash submit a Talkback crash report. After that run firefox\components\talkback.exe manually and post the Talkback ID from that crash in this bug. marking wfm based on the comments (4x wfm)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 9•20 years ago
|
||
Couldn't get Talkback to respond, or even run manually report, on the crash. Attachement is zipped DrWatson log of Firefox crashes...
You need to log in
before you can comment on or make changes to this bug.
Description
•