Closed
Bug 329175
Opened 19 years ago
Closed 19 years ago
Firefox crashes after memory upgrade
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: welshans2, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
I have been running a Gateway with no problems with 512Meg of ram. I upgraded to 1.5Gig and now it crashes frequently. It does not matter what URL I am on - it seems to be random. I am also seeing Firefox hand at times now, and I can exit using the TaskManager.
I have tried using IE for a day to see if it would run OK, and it does. The computer is a Gateway with an Athalon 1.1 /133. The memory is three PC133 512Meg SDRAM. (Max allowed on the motherboard)
Reproducible: Sometimes
Steps to Reproduce:
1.Open any web page
2.Navigate around and find a download (more than a couple meg)
3.Continue navigating.
Actual Results:
Firefox may or may not close, if it does it sends a crash report to Mozilla. When it crashes, Firefox.exe continues as a task and I either use Taskmanager to shut it down or if it hangs, I shut the machine down by holding the reset button in.
It may also hang and I shut it down with the TaskManager.
Expected Results:
I did not expect the browser to hang or crash.
Comment 1•19 years ago
|
||
What happens when you try and stress your memory using a program like memtest86?
- http://www.memtest86.com/
Reporter | ||
Comment 2•19 years ago
|
||
I ran memtest86 and found two of the 512 Meg SIMMs were bad. One reported in at 256, the other was packed full of errors.
I have now replaced the two with a 256 meg and a 128 meg that were in the computer originally.
I will run it this way until replacement SIMMS arrive. Thanks for the tip. I should have been smart enough to think about the new memory being suspect. But who would think that two out of three were bad (at least so far). I will odify to fixed after I run this a while.
Regards, Terry
Comment 3•19 years ago
|
||
Glad that helped! Hope you have better luck with your next sticks of RAM.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•