MC-11037Uncapped framerate in certain screens causes high levels of GPU usage.
Minecraft's GUI screens (with no 3D rendering in the background) don't have a cap on the framerate they run at. This means that they will use up a lot more GPU power than needed.
Here's some example framerates taken from 13w10a (so I could test the texture pack screen in-game).
Title screen: 36 FPS
World List: 780 FPS
Server List: 725 FPS
Options (From Title): 785 FPS
Language (From Title): 710 FPS
Texture Packs (From Title): 785 FPS
In Game: ~95 FPS
Options (In Game): ~95 FPS
Texture Packs (In Game): ~95 FPS
Of interest is that the texture pack screen has the same forced background depending on where you access it from, but it only displays the abnormally-high framerate if you access it from the title menu (or the options screen in the snapshot).
So it's a bit more taxing for the GPU to sit at the world select screen than it is to actually play the game. 
Crash report 1 (02.35.03) is from 1.4.7.
Crash report 2 (02.38.24) is from 13w10a.
Environment
OS: Windows 7 Home Premium 64-bit
CPU: Intel Core 2 Quad Q8400
RAM: 4GB
GPU: Radeon HD 5770
(VRAM: 1GB)
Java: 1.7.0_17 (Java 7, Update 17)
Linked Issues
Created Issue:
Uncapped framerate in certain screens causes high levels of GPU usage.
Minecraft's GUI screens (with no 3D rendering in the background) don't have a cap on the framerate they run at. This means that they will use up a lot more GPU power than needed.
Here's some example framerates taken from 13w10a (so I could test the texture pack screen in-game).
Title screen: 36 FPS
World List: 780 FPS
Server List: 725 FPS
Options (From Title): 785 FPS
Language (From Title): 710 FPS
Texture Packs (From Title): 785 FPS
In Game: ~95 FPS
Options (In Game): ~95 FPS
Texture Packs (In Game): ~95 FPSOf interest is that the texture pack screen has the same forced background depending on where you access it from, but it only displays the abnormally-high framerate if you access it from the title menu (or the options screen in the snapshot).
So it's a bit more taxing for the GPU to sit at the world select screen than it is to actually play the game.
Crash report 1 (02.35.03) is from 1.4.7.
Crash report 2 (02.38.24) is from 13w10a.Environment
OS: Windows 7 Home Premium 64-bit
CPU: Intel Core 2 Quad Q8400
RAM: 4GB
GPU: Radeon HD 5770
(VRAM: 1GB)
Java: 1.7.0_17 (Java 7, Update 17)
Attachments2
is duplicated by
Attaching a screenshot to show I'm not just typoing like crazy!
Confirmed. See commented screenshot of GPU-Z
Checking my clocks with GPU-Z I've got the same sort of results, the title screen alternates between 157mhz and 600mhz, in-game is 600mhz, but for the world list it needs to clock up to 850mhz. GPU usage fluctuates as well, but the fact that our GPUs need to raise their clock speed just to show the screen shows it's not right.
Can u add some more labels to this issue? When I searched it a couple times I got no results, and created that duplicate. here are some labels:
card
coil
fps
gpu
graphics
high
menu
menus
noise,
pitched
v-sync
whine
PS coil whine is a sound created by some gpus when outputting very high FPS
Optifine limits the FPS of the menus to 35 fps, so you may want to get that for now.
But there being no limit on it is just ridiculous. Why would we need ~900 FPS on the menus?
Is this still a concern in the current Minecraft version 1.6.4 / Launcher version 1.2.5 ? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Sorry, for some reason I didn't see this notice until now.
In 1.7.2 the title screen, server list, options, and language selection screens all seem to be capped at 30 FPS, so please mark this as fixed.