Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using 24+Gb of virtual memory on Firefox/Ubuntu 20.04 #1532

Closed
6 of 8 tasks
acostaja opened this issue Mar 20, 2021 · 3 comments
Closed
6 of 8 tasks

Using 24+Gb of virtual memory on Firefox/Ubuntu 20.04 #1532

acostaja opened this issue Mar 20, 2021 · 3 comments
Labels
duplicate This issue or pull request already exists invalid not a uBlock issue

Comments

@acostaja
Copy link

acostaja commented Mar 20, 2021

Prerequisites

  • I verified that this is not a filter issue
  • This is not a support issue or a question
  • I performed a cursory search of the issue tracker to avoid opening a duplicate issue
    • Your issue may already be reported.
  • I tried to reproduce the issue when...
    • uBlock Origin is the only extension
    • uBlock Origin with default lists/settings
    • using a new, unmodified browser profile
  • I am running the latest version of uBlock Origin
  • I checked the documentation to understand that the issue I report is not a normal behavior

Description

[Description of the bug or feature]

A specific URL where the issue occurs

[A specific URL is MANDATORY for issue happening on a web page, even if it happens "everywhere"]

Steps to Reproduce

  1. [First Step]
  2. [Second Step]
  3. [and so on...]

Expected behavior:

[What you expected to happen]

Actual behavior:

[What actually happened]

Your environment

  • uBlock Origin version:
  • Browser Name and version:
  • Operating System and version:
@acostaja
Copy link
Author

using 24GB of virtual ram, if not an issue its an horrific code

@uBlock-user
Copy link
Contributor

Speculated performance issues will be marked as invalid and closed if they do not come with actual profiling data from Firefox Profiler/Chromium Profiler + fully substantiated analysis supporting the claim.

@uBlock-user uBlock-user added the invalid not a uBlock issue label Mar 20, 2021
@gorhill
Copy link
Member

gorhill commented Mar 20, 2021

Duplicate of #994 (comment).

Virtual memory usage is not physical memory usage, it's just addressable space reserved by an application. Typically on a 64-bit OS, you will have something around 256 TB (Terabytes) of addressable virtual memory, so 26 GB / 256 TB = 0.01% of addressable, non-physical memory.

It's just a side effect of uBO using WASM modules, and is completely inconsequential.

If for completely irrational reasons this virtual memory figure still bothers you, you can set advanced setting disableWebAssembly to true, at the cost of rendering uBO less performant and with nothing gained in return.

@uBlock-user uBlock-user added duplicate This issue or pull request already exists and removed invalid not a uBlock issue labels Mar 20, 2021
@gorhill gorhill added the invalid not a uBlock issue label Mar 20, 2021
@garry-ut99 garry-ut99 mentioned this issue Apr 8, 2024
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists invalid not a uBlock issue
Projects
None yet
Development

No branches or pull requests

3 participants