Closed Bug 1403782 Opened 7 years ago Closed 7 years ago

Rapidly rising RAM usage on Travis CI build output page with webrender and uBlock Origin

Categories

(Core :: Graphics: WebRender, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox57 --- unaffected
firefox58 --- unaffected

People

(Reporter: Tobbi, Unassigned)

References

Details

Attachments

(1 file)

Steps to reproduce:
1. Enable webrendest.
2. Install uBlock Origin (I'm using 1.14.10).
3. Go to a Travis CI page with a running build, at the time of this bug report, this would be https://travis-ci.org/SuperTux/supertux/jobs/280618976
4. Watch CPU and memory usage of content process rise (how fast it rises seems to depend on how often something is added to the Travis build console output).

uBlock Origin: 1.14.10
Firefox Nightly: 58.0a1 (2017-09-27) (64-Bit)
Summary: Rapidly rising RAM usage on Travis CI homepage with webrender, uBlock Origin → Rapidly rising RAM usage on Travis CI build output page with webrender and uBlock Origin
Whiteboard: [wr-mvp] [triage]
Whiteboard: [wr-mvp] [triage]
How did you end up with "assets.json" as a selected filter list?

This is *not* a filter list, and I can't make sense of how it ended up in your set of selected filter lists -- there is no way to do this through the UI, only way I can think of is to edit the backup file manually and import the result in uBO.

I don't know whether this is your issue, but importing a non-filter list resource as a filter list will cause undefined behavior. At least for sure, this causes a lot of bad, inefficient filters to be created. Please remove the entries:

    "assets.json",

... and ...

    "assets.json": {
      "off": false
    },

... from the backup file and restore into uBO. See if this fixes your issue.
(In reply to rhill@raymondhill.net from comment #1)
> How did you end up with "assets.json" as a selected filter list?
> 
> This is *not* a filter list, and I can't make sense of how it ended up in
> your set of selected filter lists -- there is no way to do this through the
> UI, only way I can think of is to edit the backup file manually and import
> the result in uBO.
> 
> I don't know whether this is your issue, but importing a non-filter list
> resource as a filter list will cause undefined behavior. At least for sure,
> this causes a lot of bad, inefficient filters to be created. Please remove
> the entries:
> 
>     "assets.json",
> 
> ... and ...
> 
>     "assets.json": {
>       "off": false
>     },
> 
> ... from the backup file and restore into uBO. See if this fixes your issue.

I just re-exported my settings and I can't find that entry in the new backup file, thus I assume whatever caused it to be in the previous backup is now fixed. Furthermore, I can't reproduce this bug anymore.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: