notepad-plus-plus / notepad-plus-plus/notepad-plus-plus

[BUG] After update, process is still heating up my computer

Open
#18,177 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
29.4k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Is there an existing issue for this?
  • I have searched the existing issues
Is the issue reproducible in Notepad++ without plugin?
  • I have tried Notepad++ without plugin
Is the issue reproducible in portable version of Notepad++?
  • I have tried portable version of Notepad++
Does the issue affect SciTE?
  • I have tried SciTE
Description of the Issue

I have as many things off as I can, but this program is still the only one taxing my RAM.

Steps To Reproduce
  1. Turn on the program.
  2. Ten windows are open. None of them are being edited.
Current Behavior

I exit the program, and the entire computer cools off within two minutes. I have tried this with everything else, and that's the only difference.

Expected Behavior

Don't destroy my computer? Why is it running something in the background? I should have everything off that tries to contact when I'm online, so what's even going on? This is a text file editor; it shouldn't have any continuous processes in the first place.

Debug Information
Unfortunately every time is an emergency - that's how hot it is - so I'm not going to turn the program back on and risk my hardware again.
Anything else?

Windows 10 Processor Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz 2.00 GHz
Installed RAM 8.00 GB
I can't find the older post at this moment, // edit: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/17132 I think this was it - but it was closed with the promise that this would be fixed in the next update. Well, it's the next update.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Start by reproducing the report on Windows 10 with ten open, idle windows and compare system activity before and after exiting; done means isolating the background work that keeps the computer busy and verifying it stops for idle instances.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.