Crash caused by vertical wiring (half slabs / glowstone / full blocks)
To reproduce:
1. Build vertical wiring "stairs" using half-slabs (or glowstone, by some reports and full blocks MC-10469)
2. Wiring should be high enough, atleast 16 blocks total.
3. Tests show that this happens most likely when wiring is aligned along X axis.
4. Trying to input redstone signal at one of the sides (usually from where X is greater) at certain height (usually closer to the top) will crash the game.
5. If you are able to relog, you will observe invalid signal travelling downwards, as in second screenshot.
Video: http://youtu.be/AZPw2Cmm9DQ
Old description:
1. Placed the redstone torch on a side of a block in certain position.
2. The redstone torch appeared, in ON state (although it should be off because the block is powered, but usually they go off in a moment).
3. The game crashed before I could do anything else.
4. Reentered the world, torch was still ON, game crashed immediately.
5. Reentered the world, torch was OFF, and game didn't seem to crash.
6. Broke the torch, didn't seem to crash.
7. Placed it again, another crash.
Since the issue seems reproducable in certain configurations only, the world save file is attached, as well as crash reports. The torch in question is the one my player is facing as per save file. Try breaking it and placing again to reproduce.
Environment
win7x64,jre7x64
Linked Issues
is duplicated by18
MC-8229game crash (redstone cause) DuplicateMC-8458Exception while updating neighborsDuplicateMC-9051Block-update induced infinite recursionDuplicateMC-9053Unexpected CrashDuplicateMC-9411redstone being powered when there is no power sourceDuplicateMC-9425Droppers dispensing into other droppers vertically and simultainiously, crashes the game.DuplicateMC-9463Crash due to redstone updateDuplicateMC-9516Crash with instant redstone not gateDuplicateMC-9827crashedDuplicateMC-9980Playing 13w07a, got same game crash twice in 10 minutesDuplicateMC-10106Game crash, always at same conditions, but not alwaysDuplicateMC-10136Server Crash with Snapshot and my custom mapDuplicateMC-10161Minecraft crashed when playing Chronotide 1.4.5 adventure pack.DuplicateMC-10469Blocks dusted with redstone acting as slabsDuplicateMC-10474Some Redstone Wire creates a crash on block update or lack thereofDuplicateMC-10559minecraft crash after a few sec STILL DuplicateMC-11481Minecraft crashDuplicateMC-15073Update exception when playing with TNT player launcher in creativeDuplicateAttachments9
Created Issue:
Consistent crashes when placing/removing a certain redstone torch
The timeline:
1. Placed the redstone torch on a side of a block in certain position.
2. The redstone torch appeared, in ON state (although it should be off because the block is powered, but usually they go off in a moment).
3. The game crashed before I could do anything else.
4. Reentered the world, torch was still ON, game crashed immediately.
5. Reentered the world, torch was OFF, and game didn't seem to crash.
6. Broke the torch, didn't seem to crash.
7. Placed it again, another crash.
Since the issue seems reproducable in certain configurations only, the world save file is attached, as well as crash reports. The torch in question is the one my player is facing as per save file. Try breaking it and placing again to reproduce.Environment
win7x64,jre7x64
Linked Issues
Attachments5
duplicates
clones
MC-8427
is duplicated by
duplicates
clones
is duplicated by
is duplicated by
Consistent crashes when placing/removing a certain redstone torchCrash caused by vertical wiring (half slabs / glowstone)
The timeline:
1. Placed the redstone torch on a side of a block in certain position.
2. The redstone torch appeared, in ON state (although it should be off because the block is powered, but usually they go off in a moment).
3. The game crashed before I could do anything else.
4. Reentered the world, torch was still ON, game crashed immediately.
5. Reentered the world, torch was OFF, and game didn't seem to crash.
6. Broke the torch, didn't seem to crash.
7. Placed it again, another crash.
Since the issue seems reproducable in certain configurations only, the world save file is attached, as well as crash reports. The torch in question is the one my player is facing as per save file. Try breaking it and placing again to reproduce.To reproduce:
1. Build vertical wiring "stairs" using half-slabs (or glowstone, by some reports)
2. Wiring should be high enough, atleast 16 blocks total.
3. Tests show that this happens most likely when wiring is aligned along X axis.
4. Trying to input redstone signal at one of the sides (usually from where X is greater) at certain height (usually closer to the top) will crash the game.
5. If you are able to relog, you will observe invalid signal travelling downwards, as in second screenshot.Video: http://youtu.be/AZPw2Cmm9DQ
Old description:
1. Placed the redstone torch on a side of a block in certain position.
2. The redstone torch appeared, in ON state (although it should be off because the block is powered, but usually they go off in a moment).
3. The game crashed before I could do anything else.
4. Reentered the world, torch was still ON, game crashed immediately.
5. Reentered the world, torch was OFF, and game didn't seem to crash.
6. Broke the torch, didn't seem to crash.
7. Placed it again, another crash.
Since the issue seems reproducable in certain configurations only, the world save file is attached, as well as crash reports. The torch in question is the one my player is facing as per save file. Try breaking it and placing again to reproduce.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
To reproduce:
1. Build vertical wiring "stairs" using half-slabs (or glowstone, by some reports)
2. Wiring should be high enough, atleast 16 blocks total.
3. Tests show that this happens most likely when wiring is aligned along X axis.
4. Trying to input redstone signal at one of the sides (usually from where X is greater) at certain height (usually closer to the top) will crash the game.
5. If you are able to relog, you will observe invalid signal travelling downwards, as in second screenshot.Video: http://youtu.be/AZPw2Cmm9DQ
Old description:
1. Placed the redstone torch on a side of a block in certain position.
2. The redstone torch appeared, in ON state (although it should be off because the block is powered, but usually they go off in a moment).
3. The game crashed before I could do anything else.
4. Reentered the world, torch was still ON, game crashed immediately.
5. Reentered the world, torch was OFF, and game didn't seem to crash.
6. Broke the torch, didn't seem to crash.
7. Placed it again, another crash.
Since the issue seems reproducable in certain configurations only, the world save file is attached, as well as crash reports. The torch in question is the one my player is facing as per save file. Try breaking it and placing again to reproduce.To reproduce:
1. Build vertical wiring "stairs" using half-slabs (or glowstone, by some reports and full blocksMC-10469)
2. Wiring should be high enough, atleast 16 blocks total.
3. Tests show that this happens most likely when wiring is aligned along X axis.
4. Trying to input redstone signal at one of the sides (usually from where X is greater) at certain height (usually closer to the top) will crash the game.
5. If you are able to relog, you will observe invalid signal travelling downwards, as in second screenshot.Video: http://youtu.be/AZPw2Cmm9DQ
Old description:
1. Placed the redstone torch on a side of a block in certain position.
2. The redstone torch appeared, in ON state (although it should be off because the block is powered, but usually they go off in a moment).
3. The game crashed before I could do anything else.
4. Reentered the world, torch was still ON, game crashed immediately.
5. Reentered the world, torch was OFF, and game didn't seem to crash.
6. Broke the torch, didn't seem to crash.
7. Placed it again, another crash.
Since the issue seems reproducable in certain configurations only, the world save file is attached, as well as crash reports. The torch in question is the one my player is facing as per save file. Try breaking it and placing again to reproduce.
Crash caused by vertical wiring (half slabs / glowstone / full blocks)
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Duplicate of MC-8426, please use the search function to see if your bug has already been submitted. Currently over 51% of tickets are being closed as duplicate.
Duplicate of MC-8426, please use the search function to see if your bug has already been submitted. Currently over 51% of tickets are being closed as duplicate.
Duplicate of MC-8426, please use the search function to see if your bug has already been submitted. Currently over 51% of tickets are being closed as duplicate.
Duplicate of MC-8426, please use the search function to see if your bug has already been submitted. Currently over 51% of tickets are being closed as duplicate.
Duplicate of MC-8426, please use the search function to see if your bug has already been submitted. Currently over 51% of tickets are being closed as duplicate.
Duplicate of MC-8426, please use the search function to see if your bug has already been submitted. Currently over 51% of tickets are being closed as duplicate.
My apologies, I wasn't sure if this bug was the same as MC-8426, the effects on an x64 computer are quite different (the repeater is turned on without any power but not the others, as seen in the pictures)
Duplicate of MC-8426, please use the search function to see if your bug has already been submitted. Currently over 52% of tickets are being closed as duplicate.
Based on a crash report provided in this issue, I believe with high certainty that this report may be a duplicate of
MC-8229. If I am wrong, please go yell at Dinnerbone.Based on a crash report provided in this issue, I believe with high certainty that this report may be a duplicate of
MC-8229. If I am wrong, please go yell at Dinnerbone.Based on a crash report provided in this issue, I believe with high certainty that this report may be a duplicate of
MC-8229. If I am wrong, please go yell at Dinnerbone.Regardless what the bot is saying three times: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.Sorry my fault, read the wrong crash report.
Reopened.
The crash seems to be caused by half-block vertical wiring array... I can't seem to find a workaround, it keeps crashing in both of the cases:
1. When I place the torch in front of a wire.
2. When I remove the wire, place the torch, place the wire and then power the torch.
Can anyone confirm using the save file?
Confirmed with the attached world.
Still present in 13w05a
And in 13w05b.
Note that this is a rather critical issue that can render worlds unusable; I cannot load my world anymore because it crashes immediately.
New easy method of recreating this bug - build a vertical half-slab wiring along X axis like in second screenshot, placing a torch next to that wiring from a certain side at a certain height is likely to produce this crash. If you are able to reload into the world you will observe invalid redstone signal travelling down, which is probably the real cause of the crash.
I can also reproduce. Built a slab tower, put down a redstone torch next to one of the pieces of redstone dust, took it away (everything was still fine), removed the dirt block it was on and got the crash.
Still present in 13w06a
the game crashes also when powering off a redstone signal going into a glowstone tower that is 10 blocks high. And this is quite a big problem becouse this kind of tower is used in a lot of stuff (13w06a)
Note:
From my cheaty source decompilation, I know that anr is the class that detects if Minecraft is modded. At least that's what it is in 13w06a. I have yet to figure out about zo, except that it extends zu.This exact crash happens randomly in my new elevator cores...the problem is that it is random. Most of the switchable circuits work without crashing, while some crash constantly, and a few others crash at times and not others. I'm using vanilla Minecraft, and the schematic file can be found at the bottom of the second post here: http://www.mcschematics.com/index.php?topic=14787.0
@James W
The crash occurs with Redstone on stairs/slabs/glowstone. The crash doesn't occur in some earlier versions. (13w03b, I think).
@William Pearson
Unfortunately, half slabs allowing signals to travel up to another block level in direct sequence is necessary in keeping the cores small. Also, the last snapshot that I could use such a piston device was 13w03b, but redstone characteristics changed, forcing a redesign. This version won't work on the older snapshot, and vice-versa. Makes sense that I didn't run into this bug before... https://mojang.atlassian.net/browse/MC-8198 kept me from working with the project until it was resolved.
Edit: forgot to state that all levels use half-slabs, but only a few cause the crash.
Decompiled, ANR is redstone, and ZO is block update. Don't know how I got what I did before.
This updates the redstone wire itself again, again and again. Ahh, this is annoying.
Attached another crash report (with 13w07a class obfuscation codes). That means this problem still occures on 13w07a.
I've found that half-slabs are not even required to cause the crash. It also happens when a repeater is pushing a signal to redstone on top of a block it's facing into, and redstone on the other side of the block at the same time.
At least, that's what's happening in some of my elevator cores.
This is still reproducible in 13w09a.Well, actually it's different in 13w09a. When doing this on a server, the server doesn't crash completely anymore. However, the server.log contains this:
Still present in 13w09b.
For something advertised as a redstone update, one would expect this to be deemed a priority issue... :-/
I wasn't able to reproduce this issue in my test setups with 13w09c anymore; from what I can tell this therefore seems to be fixed.
Fixed in 13w09c. I tested this in an old world that crashed with the older snapshots and Jeb said on reddit that he would have fixed it
Resolving as fixed.
Well, actually it still happens in 1.6 pre-release. I was playing Vechs' map "Super Hostile #08 - Nightmare Realm" and there is one area that features many traps formed by snow "slabs" which disappear upon block update. As I broke a block, it caused a mass block update that crashed me. I tried switching to Creative to see if it still happened, which it did. 14 crashes in under 10 minutes.
Quote crash report: "Description: Exception while updating neighbors"
Figured I should let you guys know, as this is listed as "resolved", and if I post the bug, it will probably be taken down as a duplicate.
Post it separately. It will help more.
How much snow did vechz place?
Well... a lot. I'd say about at least a 40x40 area, but I've played his map a couple of times in 1.5.1 and 1.4.7 and it didn't crash... not sure though.
Now posted new bug as "Crash Upon Repeated Block Update". Affects 1.6 and 1.6.1. Game mode 0 and 1 are both affected.