Firefox Process Not Exiting
J. Seth Henry
jshamlet at comcast.net
Mon Feb 16 11:49:32 PST 2004
> Date: Mon, 16 Feb 2004 09:17:46 -0500
> From: "Daniel R. Curran" <drc7257 at cs.rit.edu>
> Subject: Re: Firefox Process Not Exiting
> To: freebsd-questions at freebsd.org
> Message-ID: <4030D10A.6060704 at cs.rit.edu>
> Content-Type: text/plain; charset=us-ascii; format=flowed
> Seeing as the problem would now seem to be in the linuxpluginwrapper or
> linux-flashplugin port is there a way to fix this problem? Is there any
> work being done on it? is it a known bug? What would the process be for
> one to get the ball rolling towards a fix?
> Matthew Seaman wrote:
> >On Mon, Feb 16, 2004 at 09:15:43PM +1100, Gautam Gopalakrishnan wrote:
> >>On Mon, 16 Feb 2004 00:12:56 -0500
> >>"Daniel R. Curran" <drc7257 at cs.rit.edu> wrote:
> >>>I am wondering if anyone else has this issue and if there is a fix for
> >>>it. When I run firefox and then exit the program the process remains
> >>>resident, and it starts eating up the CPU. Does anyone know of a fix
> >>>for this. I have been manually killing the process, but this seems
> >>>like a horrible way to work with the program.
> >>One more vote from me. Same behaviour with firebird too. So it's not
> >>newly introduced...
> >I've seen this happen with all of Mozilla, Firebird and now Firefox.
> >It's only certain web sites that trigger the effect, and it seems to
> >happen on sites which make use of a large amount of Flash stuff -- the
> >effect is even caused by Macromedia's test page at
> >http://www.macromedia.com/shockwave/welcome/ -- although quite often
> >what happens is that the flash infexted page will only load once (if
> >at all) and after that the whole browser freezes up and has to be
> >killed from the command line.
> >I'd say it's more likely a bug in the linuxpluginwrapper or
> >linux-flashplugin ports.
> > Cheers,
> > Matthew
If it is the plug-in, then it affects more than just Linux/*BSD. I had this
same problem occur on a Windows box the other day. My fiancee, a diehard
AOL'er, sent me an e-card, and when I closed Mozilla after viewing it, the
window closed, but I had a mozilla process sucking up all available cycles. I
noticed this because the CPU fan went from its normal 55% on, to full up
IOW - it may be something in Mozilla/FireFox itself. Unfortunately, Mozilla
didn't technically crash, so I'm not sure how useful a bug report would be.
More information about the freebsd-questions