1867437 - Tab deadlocks consuming 100% CPU in RandomizePixels

Status: RESOLVED DUPLICATE of bug 1866409

(Core :: Privacy: Anti-Tracking, defect)

Description

[Jeremy Linton]

Attachment: firefox100percent.png

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0

Steps to reproduce:

Just upgraded to 120.0 on fedora 38.
Duckduckgo, search from firefox search box.
Modify search in the text box on the duckduckgo page hit enter.
Repeat the previous operation a couple times.

I have, the following plugins:
Auto Tab Discard
Cookie Autodelete
Firefox MultiAccount containers
HTML validator
ublock origin
and
Dark Reader, as well as firefox in dark mode.

Excuse: Dark reader does a better job on some pages than firefox does of inverting the colors.

Actual results:

After a short while the tab will stop responding, typing in the text box fails, clicking anything fails, typing in the firefox search works but nothing happens, etc. Top shows 100% CPU utilization. Cpu at max frequency, bad things happening. Its possible to open another tab, and jam up another core.

Attached is a screen grab of the about:process profile screen capture, where about:process shows the duckduckgo tab at 100%.

I killed all my plugins in re-enabled them one by one, and it seems that darkreader is at least partially the trigger here. If I enable it, but disable it on duckduckgo the browser pigs the core for a couple seconds but then operates as normal.

Expected results:

Browser should not hog my cores, or stop responding.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Jeremy Linton]

Possibly a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1866409

Comment 3

[Jeremy Linton]

I tested the fix from that other bug and it appears to have fixed my problem as well. Sorry for the noise, as presumably if I hadn't typed pizels it would have found that bug when I opened this one.

I would duplicate it myself, but apparently I don't have sufficient permissions to duplicate against a closed defect.