Codeberg/Community
54
325
Fork
You've already forked Community
12

Idle browser is CPU busy-waiting after submitting issue comments #2190

Open
opened 2025年10月28日 14:22:34 +01:00 by tasket · 11 comments

Comment

After submitting a comment via the Web UI to any issue in my project, LibreWolf browser is consuming a lot of CPU (about 30% in a 2-CPU VM).

Closing that issue page tab stops the CPU activity.

Re-opening the same issue does not make the CPU activity resume... until I post another comment.

### Comment After submitting a comment via the Web UI to any issue in my project, LibreWolf browser is consuming a lot of CPU (about 30% in a 2-CPU VM). Closing that issue page tab stops the CPU activity. Re-opening the same issue does not make the CPU activity resume... until I post another comment.
Author
Copy link

Also posting a new issue (this one) can cause the same CPU consumption problem.

Also posting a new issue (this one) can cause the same CPU consumption problem.

Hi,

Do you have the bitwarden browser extension installed?

Hi, Do you have the bitwarden browser extension installed?
Author
Copy link

No, only uBlock Origin.

(I just confirmed the issue occurs with uBO disabled.)

No, only uBlock Origin. (I just confirmed the issue occurs with uBO disabled.)

Would it be possible to profile Firefox when this happens with the "Web Developer" setting?

Would it be possible [to profile Firefox](https://profiler.firefox.com/) when this happens with the "Web Developer" setting?
Author
Copy link

I'll look into that when I get a chance. Thanks!

I'll look into that when I get a chance. Thanks!
Author
Copy link

I ran profiler for 10sec when the problem was occurring. Should I attach the profile.json.gz file here?

More about symptoms: The CPU load is split evenly about 25% for librewolf and Xorg each and GPU activity stays around 15% where normally it idles at 0%.

FWIW, I do use this browser on hundreds of different websites and don't experience this elsewhere. However, the config is a bit unusual in that its running in a VM that is configured for software-only rendering.

I ran profiler for 10sec when the problem was occurring. Should I attach the profile.json.gz file here? More about symptoms: The CPU load is split evenly about 25% for `librewolf` and `Xorg` each and GPU activity stays around 15% where normally it idles at 0%. FWIW, I do use this browser on hundreds of different websites and don't experience this elsewhere. However, the config is a bit unusual in that its running in a VM that is configured for software-only rendering.

@tasket wrote in #2190 (comment):

Should I attach the profile.json.gz file here?

Sure, if this hits the attachment size limit you should be able to upload it to https://profiler.firefox.com/ and somewhere in the top right corner you can share a link to the profile.

@tasket wrote in https://codeberg.org/Codeberg/Community/issues/2190#issuecomment-8340594: > Should I attach the profile.json.gz file here? Sure, if this hits the attachment size limit you should be able to upload it to https://profiler.firefox.com/ and somewhere in the top right corner you can share a link to the profile.
Author
Copy link

@Gusted wrote in #2190 (comment):

Sure, if this hits the attachment size limit you should be able to upload it to https://profiler.firefox.com/ and somewhere in the top right corner you can share a link to the profile.

OK.

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2190#issuecomment-8351082: > Sure, if this hits the attachment size limit you should be able to upload it to https://profiler.firefox.com/ and somewhere in the top right corner you can share a link to the profile. OK.

I don't see anything that would hint at CPU being used by codeberg.org or even in general. Could you confirm with which settings you made the profile, was it "Web Developer"?

I don't see anything that would hint at CPU being used by codeberg.org or even in general. Could you confirm with which settings you made the profile, was it "Web Developer"?
Author
Copy link

Yes, it was via "Web Developer Tools" menu item, then "Start Recording" button.

Yes, it was via "Web Developer Tools" menu item, then "Start Recording" button.

Then I'm afraid you will need to have someone that is more experienced with the Firefox browser tell you what's going on as with a fresh set of eyes this profile does not say to me there's anything wrong with codeberg.org that could explain a increase in CPU after submitting issue comments.

Then I'm afraid you will need to have someone that is more experienced with the Firefox browser tell you what's going on as with a fresh set of eyes this profile does not say to me there's anything wrong with codeberg.org that could explain a increase in CPU after submitting issue comments.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2190
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?