You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LOG:
Reported exception thrown!
net.minecraft.class_148: mouseClicked event handler
at net.minecraft.class_437.method_25412(class_437.java:495)
at net.minecraft.class_312.method_1601(class_312.java:94)
at net.minecraft.class_312.method_22686(class_312.java:165)
at net.minecraft.class_1255.execute(class_1255.java:101)
at net.minecraft.class_312.method_22684(class_312.java:165)
at org.lwjgl.glfw.GLFWMouseButtonCallbackI.callback(GLFWMouseButtonCallbackI.java:36)
at org.lwjgl.system.JNI.invokeV(Native Method)
at org.lwjgl.glfw.GLFW.glfwPollEvents(GLFW.java:3101)
at com.mojang.blaze3d.systems.RenderSystem.flipFrame(RenderSystem.java:172)
at net.minecraft.class_1041.method_15998(class_1041.java:310)
at net.minecraft.class_310.method_1523(class_310.java:1137)
at net.minecraft.class_310.method_1514(class_310.java:728)
at net.minecraft.client.main.Main.main(Main.java:217)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:568)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
Caused by: java.lang.OutOfMemoryError: Out of stack space.
at org.lwjgl.system.MemoryStack.nmalloc(MemoryStack.java:314)
at org.lwjgl.system.MemoryStack.nUTF8(MemoryStack.java:686)
at org.lwjgl.glfw.GLFW.glfwSetClipboardString(GLFW.java:4385)
at net.minecraft.class_3872.md7eec4e$lambda$onInit$0$1(class_3872.java:566)
at net.minecraft.class_4185.method_25306(class_4185.java:40)
at net.minecraft.class_4264.method_25348(class_4264.java:16)
at net.minecraft.class_339.method_25402(class_339.java:121)
at net.minecraft.class_4069.method_25402(class_4069.java:27)
at net.minecraft.class_3872.method_25402(class_3872.java:294)
at net.minecraft.class_312.method_1611(class_312.java:94)
at net.minecraft.class_437.method_25412(class_437.java:490)
... 19 more
13:24:50.599
meteordevelopment.meteorclient.MeteorClient
Thread-5
Saving
13:24:51.971
launcher
main
AL lib: (EE) alc_cleanup: 1 device not closed
13:24:51.974
monitor
Process Monitor
Process crashed with exit code -1
Steps to reproduce
get a book and quill
run bookbot
open the written book
click copy
client will crash
Meteor Version
0.4.6
Minecraft Version
1.17.1
Operating System
Windows
Before submitting a bug report
This bug wasn't already reported.
(I have checked every bug report on github)
This is a valid bug.
(I am able to reproduce this on the latest dev build)
The text was updated successfully, but these errors were encountered:
Text copying uses an off-heap LWJGL byte buffer instead of the JVM heap, so increasing the JVM's memory would have no effect. You'd have to instead increase LWJGL's default buffer size with the -Dorg.lwjgl.system.stackSize property, but that would have the side effect of increasing memory usage in other situations aswell.
Describe the bug
copying bookbot written book will crash meteor
LOG:
Reported exception thrown!
net.minecraft.class_148: mouseClicked event handler
at net.minecraft.class_437.method_25412(class_437.java:495)
at net.minecraft.class_312.method_1601(class_312.java:94)
at net.minecraft.class_312.method_22686(class_312.java:165)
at net.minecraft.class_1255.execute(class_1255.java:101)
at net.minecraft.class_312.method_22684(class_312.java:165)
at org.lwjgl.glfw.GLFWMouseButtonCallbackI.callback(GLFWMouseButtonCallbackI.java:36)
at org.lwjgl.system.JNI.invokeV(Native Method)
at org.lwjgl.glfw.GLFW.glfwPollEvents(GLFW.java:3101)
at com.mojang.blaze3d.systems.RenderSystem.flipFrame(RenderSystem.java:172)
at net.minecraft.class_1041.method_15998(class_1041.java:310)
at net.minecraft.class_310.method_1523(class_310.java:1137)
at net.minecraft.class_310.method_1514(class_310.java:728)
at net.minecraft.client.main.Main.main(Main.java:217)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:568)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
Caused by: java.lang.OutOfMemoryError: Out of stack space.
at org.lwjgl.system.MemoryStack.nmalloc(MemoryStack.java:314)
at org.lwjgl.system.MemoryStack.nUTF8(MemoryStack.java:686)
at org.lwjgl.glfw.GLFW.glfwSetClipboardString(GLFW.java:4385)
at net.minecraft.class_3872.md7eec4e$lambda$onInit$0$1(class_3872.java:566)
at net.minecraft.class_4185.method_25306(class_4185.java:40)
at net.minecraft.class_4264.method_25348(class_4264.java:16)
at net.minecraft.class_339.method_25402(class_339.java:121)
at net.minecraft.class_4069.method_25402(class_4069.java:27)
at net.minecraft.class_3872.method_25402(class_3872.java:294)
at net.minecraft.class_312.method_1611(class_312.java:94)
at net.minecraft.class_437.method_25412(class_437.java:490)
... 19 more
13:24:50.599
meteordevelopment.meteorclient.MeteorClient
Thread-5
Saving
13:24:51.971
launcher
main
AL lib: (EE) alc_cleanup: 1 device not closed
13:24:51.974
monitor
Process Monitor
Process crashed with exit code -1
Steps to reproduce
Meteor Version
0.4.6
Minecraft Version
1.17.1
Operating System
Windows
Before submitting a bug report
This bug wasn't already reported.
(I have checked every bug report on github)
This is a valid bug.
(I am able to reproduce this on the latest dev build)
The text was updated successfully, but these errors were encountered: