MesterMan03

General format: /particle <any particle> ~ ~ ~ 0 0 0 1 <high number> force @s
Examples:
/particle <any particle> ~ ~ ~ 0 0 0 1 100000 force @s
/particle <any particle> ~ ~ ~ 0 0 0 1 1000000 force @s
/particle <any particle> ~ ~ ~ 0 0 0 1 10000000 force @s

None of the settings seem to matter, as long as the particle gets rendered by the player and the count is high enough, the hang will occur. (force is used here to make sure the particle bypasses the video settings)

Usually around 10 million will hang the client for a considerably long time.

Hey, here is everything you asked for:

• The client reports an OutOfMemoryError when there are too many particles (this log is taken directly from the recorded video):

[11:42:25] [Server thread/INFO]: [RealMester: Displaying particle minecraft:angry_villager]
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Server thread"
[11:42:41] [Render thread/WARN]: Failed to get system info for Memory (heap)
java.lang.OutOfMemoryError: Java heap space
[11:42:45] [Render thread/WARN]: Could not spawn particle effect net.minecraft.core.particles.SimpleParticleType@46ea78f0
[11:42:45] [Render thread/INFO]: [System] [CHAT] Displaying particle minecraft:angry_villager

• System specifications are provided in the debug menu in the video.

• This bug is server-independent, it can be replicated on the internal server, but also on the dedicated vanilla server or 3rd party ones.

• By “Custom particle packets” I generally meant any particle packet that doesn’t naturally appear during vanilla gameplay and therefore had to be manually constructed. The /particle command can achieve the same thing since it just provides a user-facing command to create a particle packet with user-provided parameters.

seed?