InformAction Forums

FlashGot any latest versions (Mozilla Firefox 3.6.10-11) on FreeBSD x64 8.1-p1 Rel makes one of CPUs works at 100%. If I disable it in plugings - everything is OK.

Thanks

What's the process reported at 100%, exactly?

That's weird.
Does it happen also on a clean profile, with just FlashGot installed & default options?

fresh installed system, options non default, but I don't change anything extraordinary, just set a path for downloads at another (accessible location) and change start page + add browser bookmarks

Guest wrote:fresh installed system, options non default, but I don't change anything extraordinary, just set a path for downloads at another (accessible location) and change start page + add browser bookmarks

No extensions except FlashGot?
Could you check on a clean profile anyway?

I already done, what's why I reinstall OS

But now except FlashGot there are flashplayer and adblock, but disabling them nothing changed. Only FlashGot troubles me.

indb wrote:I already done, what's why I reinstall OS

Reinstalling the OS to have a clean browser profile is definitely overkill (see the linked article).

indb wrote:But now except FlashGot there are flashplayer and adblock, but disabling them nothing changed. Only FlashGot troubles me.

I actually suspect it's https://bugzilla.mozilla.org/show_bug.cgi?id=595823
Could you check whether turning download manager autodetection off (by switching flashgot.detect.auto to false in about:config) helps?
If it does, then it's very likely the aforementioned networking bug caused by JDownloader autodetection making a request to http://localhost:9666/

I have that bug with local hosts too, but internet addresses works flawless.
I turned off autodetection and for now I didn't see any cpu overload, but I need to test it more, because problem can disappear for a while and when come back again after I re-open browser several times (already try it). But now its OK.

And I don't have any downloaders installed yet (can you advise me anyone that fits best?)

seems that everything is OK now

It is a bug in FireFix itself.
IT happens with ervery connection to localhost.

See:

https://bugzilla.mozilla.org/show_bug.cgi?id=595823