Closed Bug 457101 Opened 17 years ago Closed 15 years ago

firefox killed/freezes by Ogg Vorbis audio button link at Wiktionary.org

Categories

(Firefox :: General, defect)

x86
Windows Vista
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: niborjus, Unassigned)

Details

(Whiteboard: [CLOSEME 2010-11-01])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.2) Gecko/2008091620 Firefox/3.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.2) Gecko/2008091620 Firefox/3.0.2 for the last few versions of Firefox, the pronounce button/link on wikitionary.org kills/freezes all firefox windows when it's clicked. The site seems to suggest that the button/link is to an Ogg Vorbis file. Internet Explorer works fine. Though, it does pop up the bar saying that the web site wants to run the add on: VLC media player, maybe just because ogg files are associated with VLC on my system, but it still plays the recording back even if I don't click the bar to allow that to run. Reproducible: Always Steps to Reproduce: 1. Go to: wiktionary.org 2. look up a word 3. go to the bottom of the screen where there is a button to hear the pronunciation of the word and click that button/link Actual Results: Firefox will immediately freeze all of it's windows and the program must be forceably canceled. Expected Results: Audio plays from the site.
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
Wiktionary.org changed their control, but it's still OGG. In any case, it's working fine now.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.