ok so its not a glitch and its soul sand not sandstone

maybe the soul sand is minecraft's "blood" and you're further breaking the head, making "blood" spill all over (Remember, you killed that mob).

Correction: Those are soul sand particles and this is not a bug/glitch I've know n this forever.

here is a crash glitch --- BEGIN ERROR REPORT 5cdef1ef --------

Full report at:

/Network/Servers/dms1.fcasd.edu/Volumes/Data/DMS-AF/2018/forbes_restifo_zachary/Library/Application Support/minecraft/crash-reports/crash-2012-11-16_11.42.43-client.txt

Please show that file to Mojang, NOT just this screen!

Generated 11/16/12 11:42 AM

-- System Details --

Details:

Minecraft Version: 1.4.4

Operating System: Mac OS X (x86_64) version 10.6.8

Java Version: 1.6.0_35, Apple Inc.

Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Apple Inc.

Memory: 98358528 bytes (93 MB) / 129957888 bytes (123 MB) up to 129957888 bytes (123 MB)

JVM Flags: 0 total;

AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used

Suspicious classes: No suspicious classes found.

IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0

LWJGL: 2.4.2

OpenGL: NVIDIA GeForce 9400 OpenGL Engine GL version 2.1 NVIDIA-1.6.36, NVIDIA Corporation

Is Modded: Probably not. Jar signature remains and client brand is untouched.

Type: Client (map_client.txt)

Texture Pack: Default

Profiler Position: N/A (disabled)

Vec3 Pool Size: ~~ERROR~~ NullPointerException: null

java.lang.ArrayIndexOutOfBoundsException: -4

at a.a(SourceFile:317)

at a.a(SourceFile:304)

at bac.b(SourceFile:777)

at net.minecraft.client.Minecraft.J(SourceFile:604)

at net.minecraft.client.Minecraft.run(SourceFile:534)

at java.lang.Thread.run(Thread.java:680)

--- END ERROR REPORT a89b6129 ----------