HIGH CPU usage of xfce4-terminal
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
mpv Information
mpv v0.40.0 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
libplacebo version: v7.351.0
FFmpeg version: 7.1.1
FFmpeg library versions:
libavcodec 61.19.101
libavdevice 61.3.100
libavfilter 10.4.100
libavformat 61.7.100
libavutil 59.39.100
libswresample 5.3.100
libswscale 8.3.100
Other Information
184615 smooker@st ~ $ cat /etc/os-release | grep "NAME"
NAME=Gentoo
PRETTY_NAME="Gentoo Linux"
184642 smooker@st ~ $ uname -a
Linux st 6.15.5-gentoo-dist #1 SMP PREEMPT_DYNAMIC Sun Jul 13 16:17:55 EEST 2025 x86_64 Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz GenuineIntel GNU/Linux
184701 smooker@st ~ $ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (rev 02)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU106GLM [Quadro RTX 3000 Mobile / Max-Q] [10de:1f36] (rev a1)
184746 smooker@st ~ $ glxinfo -B | grep "OpenGL version string"
OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.1.5
Reproduction Steps
--no-config : does not help :)
--no-terminal : everything is OK.
Expected Behavior
about 1% of 1 CORE/THREAD.
Imagine I was on 19200 terminal.
Actual Behavior
about 15% of 1 CORE/THREAD, because of CRAZY refresh rate of the terminal.
Log File
not GPU related. CPU Usage is from terminal emulator.
Sample Files
No response
I carefully read all instruction and confirm that I did the following:
- I tested with the latest mpv version to validate that the issue is not already fixed.
- I provided all required information including system and mpv version.
- I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of
--log-file=output.txt. - I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
- I attached the full, untruncated log file.
- I attached the backtrace in the case of a crash.
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 reproducing the report on Linux with the reported mpv version, comparing normal operation with --no-terminal and --no-config while observing terminal CPU usage. No source files or tests are identified; done means identifying the cause of the terminal refresh behavior and reducing usage toward the expected level without breaking terminal output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100