Closed
Bug 321421
Opened 19 years ago
Closed 14 years ago
firefox hangs after i close a CNN.com video
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: h, Unassigned)
References
()
Details
(Keywords: hang, stackwanted, top100)
User-Agent: Mozilla/5.0 (compatible;MSIE 5.5; GNU/Linux) Build Identifier: Mozilla/5.0 (compatible;MSIE 5.5; GNU/Linux) firefox hangs indefinitely (needs to be killed -HUP) after i play a video on cnn.com and click the close button. FreeBSD 5.4-STABLE #0: Wed Nov 23 firefox-1.5_5,1 from ports mplayer-gtk-esound-0.99.7_7 mplayerplug-in-3.17 Reproducible: Always Steps to Reproduce: 1. go to edition.cnn.com 2. watch a video next to an article 3. click the close window button Actual Results: firefox hangs Expected Results: window should close
Comment 1•18 years ago
|
||
*** Bug 344865 has been marked as a duplicate of this bug. ***
Comment 2•18 years ago
|
||
I can see this bug, using latest branch builds (1.8.0.6 and 1.8.1) on windowsxp. I have the windows media player 10.00.00.4036 plugin.
with mplayer, firefox now crashes if i close the video right after it ends. if i wait it starts again, or close it before it ends, the video shuts down properly.
Comment 4•18 years ago
|
||
So this happens only when I have Firebug installed, I suspect I see a different bug as the reporter here, since he is on Linux.
Comment 5•18 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 This works for me using mplayerplug-in 3.17 and the Ubuntu mplayer package (0.99). If you're crashing, could you install the Firefox debug package and start Firefox in a debugger and get a stack from the crash?
Keywords: stackwanted
No the bug happens in FreeBSD, not Linux. At some point in the versions, the video crashed 50% of the time, then it would crash everytime (by then I filed the bug report), now it only crashes if I close the video right after it ends. It won't crash if I let it loop, then close it. I don't see the firebug package in FreeBSD ports
reporter: firebug is not what was being asked of you. either download the mozilla sources and manually build w/ --enable-debug --disable-optimize --disable-strip.(this isn't hard, it's documented) or ask the fbsd ports system to build mozilla w/ --enable-debug --disable-optimize --disable-strip. firebug is an extension which you can install at a later date, but it's clearly a red herring.
I can do that, but since firefox actually hangs (pardon me I used the word crash lately) when i close the plugin video, how am i gonna get the log after i kill -HUP firefox? look for a .core file?
once you have symbols, you can simply attach a debugger and use it to get a stack trace. no need to bother killing it, it's not like it's going anywhere :).
Reporter | ||
Comment 10•18 years ago
|
||
tmi
Comment 11•16 years ago
|
||
reporter has moved from FreeBSD to Mac, where the problem hasn't been seen. Leaving disposal of bug to those of you who've been following the bug. If this still exists, STM it's not likely to be a top100 anymore
Severity: major → critical
Comment 12•14 years ago
|
||
(In reply to comment #11) > reporter has moved from FreeBSD to Mac, where the problem hasn't been seen. > > Leaving disposal of bug to those of you who've been following the bug. If this > still exists, STM it's not likely to be a top100 anymore after 2 years, this action seems overdue, so => incomplete
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•