Frans wrote on Aug 1, 2020, 03:58:

eRe4s3r wrote on Jul 31, 2020, 21:15:
It's fixed now on top of uBlock Origin filter-lists blocking it.

No idea what you're saying here, please elaborate.

eRe4s3r wrote on Jul 31, 2020, 21:15:
But yeah, good example of malicious ad networks.

Accusing anyone is premature. It's not even sure this problem (experienced by only a handful of people so far) is caused by the ad script, let alone intentionally and with malice.
There's also a theory that FF79 introduced something (coincidentally around the same time as the ad script was updated) which now throws a wrench in the works.

I mean that uBlock Origin now blocks more than it did when I made this topic and the file was updated the past 10~ hours. instead of 26 allowed JS instances it was 28 for 3 days. Whatever it was it's gone. And so is my interest since I can't trace it now when I have the time to actually do it.

eRe4s3r wrote on Jul 31, 2020, 21:15:
It's fixed now on top of uBlock Origin filter-lists blocking it.

No idea what you're saying here, please elaborate.

eRe4s3r wrote on Jul 31, 2020, 21:15:
But yeah, good example of malicious ad networks.

Accusing anyone is premature. It's not even sure this problem (experienced by only a handful of people so far) is caused by the ad script, let alone intentionally and with malice.
There's also a theory that FF79 introduced something (coincidentally around the same time as the ad script was updated) which now throws a wrench in the works.

It's fixed now on top of uBlock Origin filter-lists blocking it. But yeah, good example of malicious ad networks.

1. What's the exact URL? https://www.bluesnews.com ?

2. Have you tried it in Chrome or Edge? Same issue?

3. Have you tried it in FF in a Private window?

4. Happening on another device? For example, tried on FF on mobile?

5. I assume you've cleared the FF cache and rebooted?

This also happens on my Debian stable system with Firefox 60.8 installed. One core is maxed out and the memory usage keeps increasing.

Since Frans asked me

Here is my original post from that other topic.

------

I hope I can type this in time, but whenever I open this page I get a full core maxed out and infinitely increasing ram footprint of the firefox thread responsible for this page. Yes, I am talking I can literally watch the ram usage increase till it crashes without doing ANYTHING

I have to disable javascript entirely to make it stop blowing up.

That's on Firefox 79, with or without adblocker active. It's one of the javascript files that loads here not ad related

Edit. File in question is networkn.min.js (maybe?) I can't actually figure it out properly, as I said, it pushes around 800mb into ram in less than 5 seconds, if I capture I get.. a trillion billion out of memory errors for the site debugger)
It ends up in an infinite iterative stacking loop

Helps

-----

But just to be clear, I can't figure out which JS is doing it exactly because the moment I open the debugger it blows up (like literally, the debugger says memory full and stops recording, which is.. not helpful ;/

And this is how it looks then https://imgur.com/a/vUfkEaM
it blows up to the limit and crashes. The 2nd number after memory use is page-faults

Note. When I open site-inspector and hit "record memory footprint" it never records, and crashes. So yeah..

Edit: second day report - still can't figure out what's doing it, it's doing it with uBlock origin on/off too. The moment I activate JS on this page I get this issue. The only JS that I can see that runs is the one I mentioned, but it's A) not blocked by uBlock Origin and B) just because it's the one I see, doesn't mean it's the one that does it, because everything breaks AFTER that entry and I can't tell anything apart once it starts going through the roof. JS caused it, but internally firefox claims this a "GC" event. So you can guess how that looks in the debugger.. hint: it doesn't, because you can't record GC events when 130k of them happen per second ;p

This comment was edited on Jul 30, 2020, 20:59.