Closed
Bug 290996
Opened 20 years ago
Closed 17 years ago
error message "memory could not be read" when closing Firefox
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: melin44116, Unassigned)
Details
(Whiteboard: CLOSEME - 06/24)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Ever since upgrade from 3.0.1, the message "FIREFOX.EXE - APPLICATION ERROR" appears upon closing Firefox. The description of the error message is "The instruction at 0x74721ff8 referenced memory at 0x0f41200b0. The memory could not be read. Click on OK to terminate the program. After clicking OK, then the running program must be cancelled in the running programs window. Reproducible: Always Steps to Reproduce: 1.Close Firefox, view the error message, delete the error message. 2.Depress ALT CTL DELETE keys to open the progam status window and then terminate the running program 3. The error message then re-appears and has to be closed again. Actual Results: The program closes, and my desktop screen appaears. Expected Results: found the memory and no message would have appeared.
Comment 1•20 years ago
|
||
I have a similar error, also since upgrading to 1.0.3. But my error/crash doesn't always reproduce. When quiting firefox it states: The instruction at "0x4b5c8e2c" referenced memory at "0x23aea0a1". The memory could not be "read". Firefox actually does quit, unlike for melin44116@yahoo.com.
I have also been experiencing this error message. I upgraded to build 1.0.4 and the problem still exists. I cannot consistantly reproduce the error, but it seems most common after viewing a page that has embedded windows media, though it is possible that the error is in reponse to javascripting that controls the parts of the page. (In reply to comment #1) > I have a similar error, also since upgrading to 1.0.3. But my error/crash > doesn't always reproduce. When quiting firefox it states: > > The instruction at "0x4b5c8e2c" referenced memory at "0x23aea0a1". The memory > could not be "read". > > Firefox actually does quit, unlike for melin44116@yahoo.com.
Comment 3•20 years ago
|
||
Reporter, does this happen when you visit a webpage using windows media player as a plugin?
Yes, it does. I have looked for information regarding the Windows Media plugin, but didn't get far. Suggestions? (In reply to comment #3) > Reporter, does this happen when you visit a webpage using windows media player > as a plugin?
Comment 5•19 years ago
|
||
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/
Comment 6•19 years ago
|
||
My system also STILL gives this error message when exiting. Does Firefox have any comment?
Comment 7•19 years ago
|
||
works for me in Firefox 1.5 beta 2
Comment 8•19 years ago
|
||
Disabling the extension "SessionSaver" seems to have fixed this error for me. I'll report back if it still pops up.
Comment 9•18 years ago
|
||
This happens EVERY time I close the browser. I do have the very latest browser, which I downloaded this morning. But the error started happening several months ago. The specific error that pops up is: Instruction @0x019a7bc3 referenced memory at 0x019e1148. Memory could not be read.
Comment 10•18 years ago
|
||
Reporter (and anyone else having this issue), what extensions are you using? Does the problem still happen in Safe Mode? (http://kb.mozillazine.org/Safe_mode)
Updated•18 years ago
|
Summary: error message "memory could not be read" when closing Firefox 1.0.3 → error message "memory could not be read" when closing Firefox
Updated•18 years ago
|
Assignee: bugs → nobody
Comment 11•18 years ago
|
||
Reporter (or anyone else having this issue), do you have any feedback re: comment #10?
Updated•18 years ago
|
Whiteboard: CLOSEME - 06/17
Comment 12•18 years ago
|
||
Reporter (and anyone else having this issue), what extensions are you using? Does the problem still happen in Safe Mode? (http://kb.mozillazine.org/Safe_mode)
Updated•18 years ago
|
Whiteboard: CLOSEME - 06/17 → CLOSEME - 06/24
Comment 13•17 years ago
|
||
No response from reporter -> INCOMPLETE Reporter, if you are still seeing this problem with the latest release of Firefox while using a clean profile or while in Safe Mode, feel free to re-open this bug. Providing a talkback ID would be helpful in that case. http://kb.mozillazine.org/Talkback
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•