Mumble Overlay, Slaughter of Frames

[Aki1024]

Title:

Mumble Overlay, Slaughter of Frames​

Launcher Version:

1.4.7​

Modpack:

FTB Infinity​

Modpack Version:

1.7.10​

Log Link:

http://www.notapplicable.com​

Details of the issue:

1924x1056px screen size, 10 fps
481x284px screen size, 10fps
FastCraft disabled, Java 8 64x - 0-1 fps
Java 6 64x - 10fps
Java 7 64x - 11fps
Java 8 64x - 10fps
Java 8, 32 bit - Launcher runs, game doesn't

Java 8, 64x, 1.5gb 10fps
Java 8, 64x, 6.0gb 10fps
Java 8, 64x, 256mb fails to launch

Java 8, 64x, Show Console? Yes, 10fps
Java 8, 64x, Show Console? No, 10fps

javaw.exe -> Set Affinity -> All checked
javaw.exe -> Set Priority -> Normal, 10fps
javaw.exe -> Set Priority -> High, 10fps

Diablo 3, Idle in town 87fps
Diablo 3, Fight 58fps

Java 8, 64x, Avast Disabled, 10fps
Java 8, 64x, Mumble overlay disabled, Mumble ignores it's own settings and keeps overlay on. pos
Java 8, 64x, Mumble closed, 39-55 fps

Minecraft Infinity startup time (with Mumble with overlay):
Maximized or Opened, 50 minutes
Minimized, 2 minutes
If the screen is visible, the updates as to what the game is currently doing for startup takes more time then the starting up itself. Could the screen update portion refuse to update more then once a second? If I play peek-a-boo with the game, minimizing it and back, then I can witness the status jump by thousands, where such a count increase would take several minutes watching it.
If I leave the game minimize, sometimes it crashes once it is done loading, so I can't just minimize and forget about it until it is done loading.

TL;DR - Having mumble's overlay on kills startup time (from 2m to 50m), and kills fps (from 55fps to 10fps). Want others to have something to Google.​