-
Notifications
You must be signed in to change notification settings - Fork 102
Open
Description
Prerequisites
- I verified that this is not a filter list issue. Report any issues with filter lists or broken website functionality in the uAssets issue tracker.
- This is NOT a YouTube, Facebook or Twitch report. These sites MUST be reported by clicking their respective links.
- This is not a support issue or a question. For support, questions, or help, visit /r/uBlockOrigin.
- I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
- The issue is not present after disabling uBO in the browser.
- I checked the documentation to understand that the issue I am reporting is not normal behavior.
I tried to reproduce the issue when...
- uBO is the only extension.
- uBO uses default lists and settings.
- using a new, unmodified browser profile.
Description
I've noticed it while checking recently created thread:
It occurs on the latter URL only.
It's another issue falling into category of "resource drain" issues, after previous issue wherein an internet drain was occurring:
This time there is no Internet drain, instead there is CPU & RAM drain.
This time there is no uBO logger flood, instead there is browser dev console flood.
So it seems like a technically different issue than previous, but still "resources drain" category.
I didn't investigate deeper, hence I don't know whether it's a website or a browser or uBO responsible, or a mix of them.
A specific URL where the issue occurs.
https://en.wikipedia.org/wiki/VideoSteps to Reproduce
- have
no-large-mediaenabled - visit the latter URL
- open dev console (F12)
- click "play" video
- click "play" video again
- observe dev console + windows task manager CPU & RAM usage
Expected behavior
The issue to don't occur.
Actual behavior
- notice that:
- dev console is being kept flooded by some warnings & errors stucked in an infinite loop
- in windows task manager:
- two single CPU cores are occupied by browser processes with 100% each
( I guess one is a browser process and the other is a console process)
- two single CPU cores are occupied by browser processes with 100% each
- for the both processes, RAM usage appears rapidly, collectively turning into a several GB memory leak festival in a matter of a minute
With dev console hidden, the issue is smaller: 1 CPU core utilized at 50% + 300-400 MB RAM.
uBO version
1.65.0
Browser name and version
Firefox 139.0.4
Operating System and version
Win 7 x64 SP1 Pro
Metadata
Metadata
Assignees
Labels
No labels