Closed
Bug 273867
Opened 20 years ago
Closed 19 years ago
Errors in oledlg.dll & kernel32.dll then crash when using windows media player
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: jamesgiblin42, Assigned: bugzilla)
References
()
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0 Whenever I use windows media player in firefox or mozilla when i close media player window first i get the message "firefox has caused an error in OLEDLG.DLL" if I close a media player window again i get "firefox has caused an error in KERNEL32.DLL" and firefox crashes. Reproducible: Always Steps to Reproduce: 1.open windows media player in firefox or mozilla 2.close media player window - error message 3.close media player window again - error message - crash Actual Results: as above Expected Results: closed media player window only errors in oledlg.dll & kernel32.dll
Updated•20 years ago
|
Severity: normal → critical
Keywords: crash
Summary: errors in oledlg.dll & kernel32.dll then crash when using windows media player → Errors in oledlg.dll & kernel32.dll then crash when using windows media player
This is what I'm seeing. Everytime I go to a page where they have some kind of video clip that is going to bring up Windows Media Player the player is spawned and the machine locks up. The only way I've found to regain control is to unplug the machine and plug it back in again. I can't give you a specific site, because if I try to duplicate it then the machine locks up again. Try this: go to MSN and click on one of their video clips. Here's a link you can try http://www.ahajokes.com/funny_videos.html and then click on one of the links to a video. Not sure if this will fail because I can't test - if I do them machine could lock up again... Gem
Comment 2•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 3•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•