Client crash when changing resource packs

Question

Client crash when changing resource packs

antimuffin opened this issue 7 years ago · 4 comments

antimuffin commented 7 years ago

If Quark is installed and enabled, even with all modules turned off, changing resource packs while in a game crashes the client. Disabling Quark allows resource packs to be switched mid-game as usual. This occurs regardless of which resource pack is used, or even just removing a resource pack to return to vanilla textures.

The client doesn't crash with Quark loaded if you change resource packs from the main menu instead of inside a game.

Playing on Minecraft 12.2 with Forge 14.23.0.2486 with Quark r1.4-120. Installed via Curse Client.

The modpack I'm using is Vanilla Forge 1.2.1 with non-worldgen mods added on top. Removing Quark fixes the issue entirely. Removing everything but the base Vanilla Forge and Quark retains the issue.

Strangely, having every Quark module ON changes the issue from a quick client crash into an extremely long stall followed by an eventual recovery (if you're willing to wait a few minutes).

I attempted a binary search to try to narrow down which particular module being loaded makes the difference between crash and stall, but this wasn't fruitful because having EITHER half enabled produces the crash.

antimuffin · Answer 1 · 2017-12-14T01:58:49.000Z

https://pastebin.com/Gff6Kqua

Vazkii · Answer 2 · 2017-12-13T20:33:11.000Z

I appreciate the detailed report, but you forgot the most important part: the log.

…

On Wed, Dec 13, 2017, 20:28 cmleininger ***@***.***> wrote: If Quark is installed and enabled, even with all modules turned off, changing resource packs while in a game crashes the client. Disabling Quark allows resource packs to be switched mid-game as usual. This occurs regardless of which resource pack is used, or even just removing a resource pack to return to vanilla textures. The client doesn't crash with Quark loaded if you change resource packs from the main menu instead of inside a game. Playing on Minecraft 12.2 with Forge 14.23.0.2486 with Quark r1.4-120. Installed via Curse Client. The modpack I'm using is Vanilla Forge 1.2.1 with non-worldgen mods added on top. Removing Quark fixes the issue entirely. Removing everything but the base Vanilla Forge and Quark retains the issue. Strangely, having every Quark module ON changes the issue from a quick client crash into an extremely long stall followed by an eventual recovery (if you're willing to wait a few minutes). I attempted a binary search to try to narrow down which particular module being loaded makes the difference between crash and stall, but this wasn't fruitful because having EITHER half enabled produces the crash. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#718>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABtir7XZtNDp0Z0aKu8Mz-JNXcZCE_WVks5tADNxgaJpZM4RBIZy> .

antimuffin · Answer 3 · 2017-12-13T20:49:53.000Z

Sorry. Here's a crash report with Vanilla Forge + Quark only, removing a resource pack during a game, only World module disabled.
crash-2017-12-13_13.48.12-client.txt

Vazkii · Answer 4 · 2017-12-13T21:29:35.000Z

You messed up uploading that. Put it on pastebin.

…

On Wed, Dec 13, 2017, 20:49 cmleininger ***@***.***> wrote: Sorry. Here's a crash report with Vanilla Forge + Quark only, removing a resource pack during a game, only World module disabled. crash-2017-12-13_13.48.12-client.txt <https://github.com/Vazkii/Quark/files/1557027/crash-2017-12-13_13.48.12-client.txt> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#718 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABtir1OzXVLc-8Ql4UbF3XuXZIaI4e-uks5tADhxgaJpZM4RBIZy> .

Share to