Dragging notes results in excessive CPU utilisation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 273
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
On dragging a note across the screen a large increase in CPU utilisation is noticeable, spiking up to 30% of one of my CPU's cores and sustaining near 25% for prolonged drags.
Other apps such as Alacritty peak to 3%, and pcmanfm at 1%.
This seems like it may be caused by NoteEntry.__init__ which appears to get called on every movement event.
I confirmed this by adding a simple print statement and watching the output spam with pages of logs from a simple drag across the screen.
The CPU profiling was done without the log statement present, for clarity.
Tested version: 1.2.1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating NoteEntry.init and the drag or movement-event path; confirm whether initialization runs for each movement event using the existing reproduction. Trace the update path and identify unnecessary repeated work, then verify that dragging no longer causes sustained high CPU usage without the debug print.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100