[MC-5728] Infinite loop caused by a comparator (on subtractor mode) feedback loop. Created: 03/Jan/13  Updated: 10/Feb/13  Resolved: 04/Jan/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w01a
Fix Version/s: Snapshot 13w01b

Type: Bug
Reporter: Eddy B. Assignee: Unassigned
Resolution: Fixed Votes: 2
Labels: compartor, redstone

Attachments: PNG File 2013-01-03_20.25.47.png     PNG File 2013-01-03_23.22.51.png     PNG File V4oqc.png     Text File crash-2013-01-03_18.48.48-server.txt    
Issue Links:
Duplicate
is duplicated by MC-5809 Crash when comparators make a complex... Resolved
is duplicated by MC-6065 Game Crashing When Using Comparator's... Resolved
Confirmation Status: Unconfirmed
Game Mode: Creative

 Description   

I've attached the crash log and a schematic of the circuit.

The top repeater signifies a comparator on subtractor mode, the second one is a simple comparator.

I can only assume that some missing safe-guards allowed the subtractor to update itself continuously, until the game crashed.

NOTE: if you want to reproduce this, you should place the second comparator (acting as a buffer) last, to get the exact same state.



 Comments   
Comment by Lowell Scott [ 04/Jan/13 ]

Ive had a very similar setup causing a crash as well. One comparator outputting into a second comparator which outputs directly into the side of the first. 2 comparators, 6 redstone and some sort of initial input into the loop (i.e. lever).

Comment by Sebastian Schmidt [ 03/Jan/13 ]

I can confirm this bug. It causes a stack overflow. I get the same loop between those for methods.

Comment by Axel Höglund [ 03/Jan/13 ]

I can confirm this crash. I did it in a different way though. I did it like this

x>#
x<xxi

where x = redstone, < = comparator facing the shown direction on the default setting, # = a solid block (capable of transmitting redstone power), i = redstone torch

Do not try this in a normal world as it will "corrupt" the world, until you delete it using external programs (MCEdit)

Comment by [Mojang] Nathan Adams [ 03/Jan/13 ]

I believe it's just a bug in the error reporting as java kinda fails at figuring stuff out in such extreme cases. I replicated successfully locally.

Comment by Kumasasa [ 03/Jan/13 ]

If you can reproduce this with an unmodded Minecraft, please go ahead.

Until then:
This ticket is invalid as it relates to a modded or 3rd party client/server.

  • Any non-standard client/server build needs to be taken up with the appropriate team, not Mojang.
  • Any plugin issues need to be addressed to the plugin creator.
  • This site is for addressing issues related to the base unmodded MineCraft.
Comment by Kumasasa [ 03/Jan/13 ]

The drunk bot found out:

Is Modded: Very likely; Jar signature invalidated
Comment by Eddy B. [ 03/Jan/13 ]

Go away bot, you're drunk.

Comment by [Bot] Spam Golem [ 03/Jan/13 ]

I could not find any existing issue that contains any of the crashes mentioned here. However, all of the crash reports that you have provided are from a modded version of Minecraft. Please try to reproduce the crash in a vanilla (non-modded) version of Minecraft and attach that report or this may be dismissed as being caused by a mod.

Generated at Sun Jan 12 12:08:51 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.