-
Bug
-
Resolution: Fixed
-
2.1.7658 (linux Beta)
-
None
-
None
-
openjdk version "11.0.4" 2019-07-16
OpenJDK Runtime Environment (build 11.0.4+11-post-Ubuntu-1ubuntu218.04.3)
OpenJDK 64-Bit Server VM (build 11.0.4+11-post-Ubuntu-1ubuntu218.04.3, mixed mode)
System: Kernel: 4.15.0-65-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.2.4
Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic
CPU: Topology: Quad Core model: Intel Core i7-4770R bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 6144 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 51079
Speed: 2789 MHz min/max: 800/3900 MHz
Graphics: Device-1: Intel vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1200~60Hz
OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.0.8 direct render: Yes
openjdk version "11.0.4" 2019-07-16 OpenJDK Runtime Environment (build 11.0.4+11-post-Ubuntu-1ubuntu218.04.3) OpenJDK 64-Bit Server VM (build 11.0.4+11-post-Ubuntu-1ubuntu218.04.3, mixed mode) System: Kernel: 4.15.0-65-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.2.4 Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i7-4770R bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 6144 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 51079 Speed: 2789 MHz min/max: 800/3900 MHz Graphics: Device-1: Intel vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1200~60Hz OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 19.0.8 direct render: Yes
-
Unconfirmed
Manually installed MCL 2.1.7658 via Minecraft.deb on Linux Mint 19.2 after purging MCL 2.1.5965. Immediately noticed higher CPU usage after clicking "Play" (both on the menu screen and while playing).
System Monitor is showing a considerable amount of kernel CPU use when Minecraft is running - this was not happening on MCL 2.1.5965.
Purged the new launcher and went back to MCL 2.1.5965 and Minecraft behaved normally again.