Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

Specific Firefox process has very high CPU usage, causing my system to stay constantly spiked at 100% (and consequently get very hot)

  • 3 trả lời
  • 1 gặp vấn đề này
  • 7 lượt xem
  • Trả lời mới nhất được viết bởi FredMcD

more options

This is being categorized as privacy and security issues since every other search I've done for such issues point to plugins or datamining/cryptomining viruses. I've done every possible scan for my system for viruses and nothing popped up, I've browsed Explorer manually for all the files and any possible anomalies, and nothing strange has come up.

I've attached an image of the specific process that is doing this. I would like actual help, not just "check your plugins" or "run an AV scan" or something of that sort. If it's an obvious troubleshooting step, I've already tried it to no avail. Not trying to be rude, I just don't like "support experts" that give super obvious advice when it's clear the asker already has knowledge of it.

Some further clarifications:

  • Once ended through task manager, the process does not run again until I reboot my computer.
  • Forcing it to shut down through the task manager does not close my firefox if it's open, nor does it affect it in any functional way from my observations. This process is seemingly entirely useless, which only further raises suspicion.
Đính kèm ảnh chụp màn hình

Được chỉnh sửa bởi Revontulet vào

Tất cả các câu trả lời (3)

more options

Diagnose Firefox issues using Troubleshoot(Safe) Mode {web link}

A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?

more options

FredMcD said

Diagnose Firefox issues using Troubleshoot(Safe) Mode {web link} A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?

Unfortunately, yes. As in previous tests of this, the process in question is apparently completely seperate from the "proper" Firefox process, which ties into bullet point 2 of my additional observations... It's an entirely pointless process that serves no other purpose than to melt my CPU.

more options