On Wed, 03 Jun 2009 07:41:38 +0930, Tim wrote:
On Sun, 2009-05-31 at 06:09 +0000, Thufir wrote:
> It happened again, and I tried to kill totem through "top", but it kept
> saying "no such process ID", so I fired up the Process Monitor GUI and
> was unable to kill it from there, too. It appeared to simply re-spawn
> with a different PID (?). So, I uninstalled it
I can imagine that if you have a page trying to load media in the
background (e.g. adverts that cycle through playing different media
files), it's possible that it could keep on getting called up.
Right, but that couldn't have been it for several reasons. Chiefly, it
was totem-something which was hogging the CPU, and secondly I navigated
to a simple home page without any of that and had no other open tabs or
windows.
> However, I kinda need it, or mplayer, or something. I'll try
mplayer
> to see if it has a similar interaction with wget, download helper and
> flashgot.
I'd imagine a similar problem. You're fixing the side effect rather
than the cause.
I'm not so sure of that. After removing totem I installed mplayer, and
its various add-ons/etc, and everything's fine. I can download a video
with flashgot (cURL seems to work better than wget for some sites) and no
real cpu problems with downloads now -- at least so far.
I use Flashblock on my browser, so I don't have to put up with
all the
nonsense on some webpages. I notice that if I disable it, allowing all
the content, again, some pages will peg my CPU as they load their crap.
If I allow just one thing to load, something I want to look at,
generally I'm fine. But, sometimes, even that one thing is enough to
bog the system down.
Yeah, that and ?noScript? seem very useful. The jerks who make those
kinds of pages are careful to keep all that intensive processing client
side, of course. However, in this case I wonder whether it's not some
subtle bug which is only apparent when the right (or wrong) combination
of apps and plug-ins are in use simultaneously.
However, I have been seeing some annoying npviewer.bin behavior, but it's
spontaneous when loading some pages, I think.
-Thufir