[FIXED,CONFLICT] FG makes Firefox download max speed

[Guest]

Dear Flashgot, I had a strange problem that when I started my firefox after a while I can find several processes download at my max rate from google servers, the ip's I have noted until now are
74.125.215.241
74.125.215.151
74.125.215.245
74.125.215.183
74.125.215.211
74.125.235.181

Once I disable the flashgot extension it stops..

[Giorgio Maone]

Dear Flashgot, I had a strange problem that when I started my firefox after a while I can find several processes

How are these processes named?
How do you watch them / measure them?
Are you using NoScript, too?
If so, which FlashGot and NoScript versions are you using, exactly?

[Guest]

Hi im using Process Hacker to watch my processes...
Only name I can see is firefox.exe

I started noticing cause I burned alot of data from my mobile phone tethering.... (2gb in 3hours)

there are several instances of firefox downloading at the max speed of my internet connection to the IP's mentioned before..

I have been disabling all my addons to figure out which was causing the problem and was left with Flashgot..
I tested it by enabling and disabling it a few times to see if it would cause the same effect..

Im using both noscript 2.6.7.1 and flashgot yes updated to the latest versions firefox 24...
I have uninstalled Flashgot now for the time being so can't say which version unfortunately...

The strange thing is it sometimes seems to happen just out of the blue.. without even using any google services.. but later on I could trigger it by watching a youtube video.. the IP's are not from youtube though...

Thanks for helping out!

[Guest]

Some additional information...
As far as I can remember it started after installing donotrackme addon..... the problem though is that disabling it didn't change anything... only disabling flashgot would stop this from happening.. but it might be related to the combination of donotrackme?

[Giorgio Maone]

Im using both noscript 2.6.7.1 and flashgot

Please update NoScript to 2.6.8.3 or latest development build, this is a known and now fixed conflict.