[MC-6532] Empty hit-box created next to torch. Created: 07/Jan/13  Updated: 27/Oct/16  Resolved: 27/Oct/16

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w01b, Minecraft 1.6.1, Minecraft 14w18a, Minecraft 1.8
Fix Version/s: None

Type: Bug
Reporter: Alberto Roman Assignee: Unassigned
Resolution: Awaiting Response Votes: 0
Labels: None
Environment:

Java:7.0.100.18, Windows 7.


Attachments: PNG File 2013-01-07_11.39.04.png     PNG File 2013-01-07_11.44.55.png     PNG File 2013-01-07_21.56.53.png     PNG File 2013-07-02_21.05.46_2.png     PNG File 2013-07-02_21.05.47.png     PNG File 2013-07-02_21.05.48.png     Text File crash-2013-01-07_21.57.21-client.txt     Text File crash-2013-07-03_17.02.24-client.txt     Text File crash-2014-10-09_18.16.46-client.txt    
Issue Links:
Duplicate
is duplicated by MC-16924 Torch Hitbox Resolved
is duplicated by MC-49568 Torch hitbox flickering Resolved
is duplicated by MC-53072 Lit Redstone Torch's hitbox "dances" ... Resolved
is duplicated by MC-54249 Collision, Selection, and color glitch Resolved
is duplicated by MC-70451 Torch hitboxes flicker Resolved
is duplicated by MC-70663 Τorch randomly black boxes appear Resolved
CHK:
Confirmation Status: Community Consensus
Game Mode: Survival

 Comments   
Comment by [Mod] redstonehelper [ 27/Oct/16 ]

Is this still an issue in current versions?

Comment by Kumasasa [ 27/Nov/15 ]

Is this still an issue in the current Minecraft Snapshot 15w47c or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Comment by [Mod] Sonicwave [ 10/Oct/14 ]

Attached crash report, here is the OpenGL line:

 (OpenGL: Intel(R) HD Graphics GL version 3.1.0 - Build 9.17.10.3347, Intel 

While it was pretty prevalent a few days ago, today I was barely able to reproduce it at all . The only thing I can think of is to leave the world open for some time.

Also I did actually get notified of your comment this time . The issues don't appear in the gmail spam/trash folder (I am using Microsoft Outlook though so that may have something to do with it). Also the JIRA filter says I have over 7 pages of watched issues so that may be a problem

Comment by Kumasasa [ 09/Oct/14 ]

@ericz1: Test Test ONE TWO THREE - Can you hear me ? IDK why you don't get notified.. Spam folder?

At least your Java is slightly outdated, 1.7.0_67 is the current version. But can't imagine that this might have something to do with the hitbox issue. What graphics card / driver do you have ? ("OpenGL" from forced crash) ?

Comment by [Mod] Sonicwave [ 09/Oct/14 ]

Upon further testing today it seems that it happens inconsistently, but occurs most often when you move the crosshair over the middle/top of the torch (try moving it around a bit and it should show up after a while). This is on my Windows 8 laptop on Java 1.7.0_55 32 bit (on a Overworld preset superflat world) so that may be a possible cause.

Also I'm not being notified via email of your comments for some reason (even though I am watching this issue).

Comment by Kumasasa [ 08/Oct/14 ]

@ericz1: Steps to reproduce ?

Comment by [Mod] Sonicwave [ 08/Oct/14 ]

Confirmed. It rapidly spazzes between the correct hitbox and the empty one.

Comment by Kumasasa [ 01/May/14 ]

Reopened due to MC-54249

Comment by Chris Koehler [ 03/Jul/13 ]

I have attached the crash report, although I do not know if it detected things right. It seems to think that I am using a modded jar, although it is vanilla. It even says no suspicious classes were found. But that may be part of the problem.

EDIT: Looking through the crash report, about all of the information about the world is wrong. The name, the seed, enabled structures, and even cheats setting is listed wrong.

EDIT2: I know what it is, I was using a different launcher. Although I have seen this bug happen with the vanilla launcher in 1.6.1 Pre.

Comment by Chris Koehler [ 03/Jul/13 ]

Crash report that seems to be bugged somehow.

Comment by Kumasasa [ 03/Jul/13 ]

Make the forced crash at any time, it's about seeing your system specs and versions.

Comment by Chris Koehler [ 03/Jul/13 ]

@Kumasasa
I am having trouble re-creating the glitch for the crash report, but I am trying to recreate the conditions it happened in. I was hosting a LAN game with 3 players at the time, and just me with the LAN game open or closed does not seem to make it happen. I am getting the same players together and I will try to recreate the bug. If it happens again I will force a crash. I have attached 3 screenshots of the bug, however.

Comment by Chris Koehler [ 03/Jul/13 ]

Screenshots of the bug. These were all taken back-to-back as fast as I could hit F2.

Comment by Kumasasa [ 03/Jul/13 ]

@Chris Koehler: Yes, please.
And please force a crash by pressing F3 + C for 10 seconds while ingame and attach the crash report here.

Comment by Chris Koehler [ 03/Jul/13 ]

I have reproduced this in release 1.6.1. I have a screenshot if interested.

Comment by Tails [ 11/Jan/13 ]

Unable to reproduce.

Comment by Kumasasa [ 08/Jan/13 ]

Try to get at newer graphics card driver, your's seems to be outdated:

OpenGL: Intel(R) HD Graphics GL version 2.1.0 - Build 8.15.10.2104, Intel

Comment by Alberto Roman [ 08/Jan/13 ]

F3 screenshot and crash-report attached.

Comment by Kumasasa [ 07/Jan/13 ]

Please force a crash by pressing F3 + C for 10 seconds while ingame and attach the crash report here.

And please attach a screenshot with the F3 debug information shown.

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