Skip to content

Schematic Cannon Memory Leak #10838

Open
Open

Description

@AlterTjempo

Description

When using the Schematic Cannon to build a schematic, a severe memory leak occurs. The server/game rapidly accumulates millions of BlockPos objects in heap memory during the placement, leading to high garbage collection latency, severe FPS drops and freezing. Eventually an OutOfMemoryError crash / disconnect. (DistantHorizons is the first victim) The game will not always forcefully shut down. Most of the time it shows as a "java.net.SocketException: Connection Reset" but after mining the schematic cannon the game get OOM errors show on screen.

Image

Here are some screenshots from the profiler:

After 5 minutes:

Image

After 10 minutes:

Image

As you can see net.minecraft.core.BlockPos grows

Game Log

https://mclo.gs/1sjgrnK (OOM-crash) & https://mclo.gs/uY5h4ko (Softcrash)

Debug Information

  1. Place a Schematic Cannon and insert a larger schematic.
  2. Supply the cannon with necessary materials
  3. Start the printing process.
  4. Observe memory usage (e.g., via Spark profiler or VisualVM). heap memory usage rapidly climbs due to uncollected BlockPos references.

Activity

  1. adaliszk commented on Nov 6, 2026

    @adaliszk
    Collaborator

    The debug information has a specific instruction you should follow:

    Please run the "/create debuginfo" command in-game. This will copy useful information to your clipboard that will greatly help with debugging. Please paste this information here.

  2. IThundxr commented on Nov 11, 2026

    @IThundxr
    Member

    Would you be able to email me the Visual VM memory report/dump (me<at>ithundxr.dev)

  3. added
    status: confirmedIssue's details are known, it is consistently reproducible, and it needs a fix
    on Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: confirmedIssue's details are known, it is consistently reproducible, and it needs a fixtype: bugIssue where something isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions