Leif
- leif_the_head
- leif_the_head
- Europe/Stockholm
- Yes
- No
MC-7812
This just happens a few seconds after reaching the main menu.
Me and my friend (both programmers) believe it depends on BufferChecks.class inside lwjgl.jar.
Game crashes a few seconds after startup -Crashreport link: http://t.co/jo2olVAi -seems to depend on BufferChecks.class inside lwjgl.jar
W 8 64bit, 8GB RAM, nvidia Geforce GTX 780M, running Minecraft from 128GB SSDNot really needed, but "beefy" enough to run at >60 fps
I spawned a regular piston (ID 33) with the orientation data 6 (which is not a normal placeable direction) per /setblock command and then just wondered what happens if you power it. Well, the game crashed, that is kinda what I expected :/
Crash log and screenshot of the piston attached.I spawned a regular piston (ID 33) with the orientation data 6 (which is not a normal placeable direction) per /setblock command and then just wondered what happens if you power it. Well, the game crashed, that is kinda what I expected :/
(Sorry if this is a duplicate, but I did not find any by using the search)
Crash log and screenshot of the piston attached.
I spawned a regular piston (ID 33) with the orientation data 6 (which is not a normal placeable direction) per /setblock command and then just wondered what happens if you power it. Well, the game crashed, that is kinda what I expected :/
(Sorry if this is a duplicate, but I did not find any by using the search)
Also I could not test if this happens in previous versions, but I believe so as you can place such a block with external tools (such as WorldEdit).
Crash log and screenshot of the piston attached.
I spawned a regular piston (ID 33) with the orientation data 6 (which is not a normal placeable direction) per /setblock command and then just wondered what happens if you power it. Well, the game crashed, that is kinda what I expected :/
(Sorry if this is a duplicate, but I did not find any by using the search)
Also I could not test if this happens in previous versions, but I believe so as you can place such a block with external tools (such as WorldEdit).
Crash log and screenshotof the piston attached.I spawned a regular piston (ID 33) with the orientation data 6 (which is not a normal placeable direction) per /setblock command and then just wondered what happens if you power it. Well, the game crashed, that is kinda what I expected :/
(Sorry if this is a duplicate, but I did not find any by using the search)The marked duplicate is closed as "invalid" as it was created using external tools. This is not
Also I could not test if this happens in previous versions, but I believe so as you can place such a block with external tools (such as WorldEdit).
//EDIT: Yes, this happens.Crash log and screenshot of the piston attached.
I spawned a regular piston (ID 33) with the orientation data 6 (which is not a normal placeable direction) per /setblock command and then just wondered what happens if you power it. Well, the game crashed, that is kinda what I expected :/
(Sorry if this is a duplicate, but I did not find any by using the search)The marked duplicate is closed as "invalid" as it was created using external tools. This is not (Note the last line of the crash report:
Also I could not test if this happens in previous versions, but I believe so as you can place such a block with external tools (such as WorldEdit).
//EDIT: Yes, this happens.Crash log and screenshot of the piston attached.
I spawned a regular piston (ID 33) with the orientation data 6 (which is not a normal placeable direction) per /setblock command and then just wondered what happens if you power it. Well, the game crashed, that is kinda what I expected :/
(Sorry if this is a duplicate, but I did not find any by using the search)The marked duplicate is closed as "invalid" as it was created using external tools. This is not (Note the last line of the crash report:Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.
Also I could not test if this happens in previous versions, but I believe so as you can place such a block with external tools (such as WorldEdit).
//EDIT: Yes, this happens.Crash log and screenshot of the piston attached.
I spawned a regular piston (ID 33) with the orientation data 6 (which is not a normal placeable direction) per /setblock command and then just wondered what happens if you power it. Well, the game crashed, that is kinda what I expected :/
(Sorry if this is a duplicate, but I did not find any by using the search)The marked duplicate is closed as "invalid" as it was created using external tools. This is not (Note the last line of the crash report:Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.
Also I could not test if this happens in previous versions, but I believe so as you can place such a block with external tools (such as WorldEdit).
//EDIT: Yes, this happens.Crash log and screenshot of the piston attached.
I spawned a regular piston (ID 33) with the orientation data 6 (which is not a normal placeable direction) per /setblock command and then just wondered what happens if you power it. Well, the game crashed, that is kinda what I expected :/
(Sorry if this is a duplicate, but I did not find any by using the search)The marked duplicate is closed as "invalid" as it was created using external tools. This is not (Note the last line of the crash report:Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.
Also I could not test if this happens in previous versions, but I believe so as you can place such a block with external tools (such as WorldEdit).
//EDIT: Yes, this happens.If you don't believe me, reproduce:
Type "/setblock ~ ~ ~ 33 6 replace"
Provide redstone power to the spawned block.Crash log and screenshot of the piston attached.
Game crashes when powering a piston with orientation data 6 (fixed)
Arrows first drop down before the player with a weird rotation, then stick in the ground, and then get moved to the expected target (just like
MC-417, which is closed with the reason "Cannot reproduce")
Difference toMC-417: The arrows keep their orientation when moved. Happens both in survival and creative.
Reproduction steps: Take a bow and shoot at a wall 5 to 20 blocks away.http://i.imgur.com/ZBpMQdP.png & http://i.imgur.com/7HCgxVZ.png
Arrows are headed weird in their target(as an addition to MC-417, where they seem to fall down and then land at the target)
Arrows first drop down before the player with a weird rotation, then stick in the ground, and then get moved to the expected target (just like
MC-417, which is closed with the reason "Cannot reproduce")
Difference toMC-417: The arrows keep their orientation when moved.Happens both in survival and creative.
Reproduction steps: Take a bow and shoot at a wall 5 to 20 blocks away.Arrows seem to bounce off an invisible block, then get ported where they should be, but keep that rotation (see pics)
Happens fewer to flame arrows, but they are also disoriented. (Note: all arrows were shot from the same spot)
Arrows first drop down before the player with a weird rotation, then stick in the ground, and then get moved to the expected target (just likeMC-417, which is closed with the reason "Cannot reproduce" Difference toMC-417: The arrows keep their orientation when moved.)Happens both in survival and creative.
Reproduction steps: Take a bow and shoot at a wall 5 to 20 blocks away.
– System Details – (Taken from a crash report)
Details:
Minecraft Version: 13w37b
Operating System: Windows 8 (amd64) version 6.2
Java Version: 1.7.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 175660352 bytes (167 MB) / 556007424 bytes (530 MB) up to 1908932608 bytes (1820 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx2048M
AABB Pool Size: 46 (2576 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Profiler Position: N/A (disabled)
Vec3 Pool Size: 2 (112 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Player Count: 1 / 8; [kp ['Leif_The_Head'/0, l='snapredtest', x=-118,97, y=56,00, z=690,96] ]
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.Win8, Java 7, more than beefy
Crashreport of that issue
Tails its definitely no Duplicate, 1.4.2 works fine for me and I got that first with 13w02a. I browsed that "Duplicate" you got there, mine is a duplicate of
MC-7174, those earlier are meant to be fixed. If this would be fixed, it wouldnt occur, does it?Sorry for my language, but this bug annoys me for a week every time I open Minecraft with this Snapshot
MC-7812andMC-7174have nothing to do withMC-872.The bug itself occurs complete other way and the third line of java in the crashreport is something complete else. I'm just going to open another ticket.
This bug also appears in 13w36b - http://i.imgur.com/xpoA3Il.jpg (in the middle between rod and crosshair)
Confirmed.
MC-30002is a duplicate.Even works with water "blocks" thou you actually can't land on them (they are a pixel lower than normal blocks) - http://i.imgur.com/9BDqtJF.png & http://i.imgur.com/WmqpbeN.png (kinda hard to see in the second one, but shows that pretty good)
Great. Gets marked as a duplicate of an year-old bug. Instead of actually trying to fix it, that is what I want. The said clone of Minecraft Terraria hasn't this bug. They first generate terrain, then adding water and finally add decorations like this. Man, this would never happen if we would be still in Alpha without any grass.
Yes. In the current snapshot.
Also affects 13w37b.
Reproduction: Take a bow, shoot. Happens both in creative and survival.
Now something additional came: The arrows' direction in at their target is not the expected but the one they had when fallen down. Made a bug report for that:
MC-30988Please reopen.
I came here because my own bug report (
MC-30973) got marked as a duplicate of this.Now my point for Kumasasa: with snapshot 13w36 and 13w37 you can place these blocks without any third party programs or mods.
It was a bit more difficult in 13w36a thou but it was possible via summoning a falling block entity with these data values. In 13w37a /setblock was added and now it is really simple to recreate: Type "/setblock ~ ~ ~ 33 6 replace" and then power the result of this.
I repeat: Reopen this as the invaild status is now invalid.
Please reopen,
MC-13252is closed as "invalid" because the block was spawned with external tools. This is spawned using the new /setblock command (and therefore using only methods Minecraft provides)I can confirm that.
Can confirm for 14w06b for Survival, Creative and Adventure mode.
and dont despawn. I think this happens because 1. it needs some time after hitting ground before you can pick up arrows, 2. they are always "moving" (flying) and the despawn timer gets resetted when an arrow moves.
When attaching that repeater to a rapid clock, the arrows also cannot be picked up
Additionally you cannot pick up arrows stuck in repeaters which are powered by a rapid clock, works the same for comparators.
(Proof for 14w06b and survival)
I can confirm that for 14w06b, this somehow does not affect flame arrows created by both shooting through lava or by flame enchantment (did not test with other enchantments yet)
Thanks for the duplicate mark, Kumasasa, didn't find this one.
Just wanted to add, this is true for all items I've tested (quite alot and should be representative), adding pics for that.
Just wanted to note: the same is for sticky pistons, but also fixed
Reopen please, can confirm that for 14w06b, screenshot added.
Just tested on 1.7.4, also happens on that.
Happens to me on upside down halfslabs, redstone blocks, hoppers and upside down stairs.
(Pic attached)
Weird levers on various blocks, applies for all "subtypes", means all kinds of stairs and halfslabs and hoppers facing all directions
Still affects current snapshot (14w25b), I assume it also affects all versions between first reported and this one.
Sorry for not keeping up to date
Can confirm for 14w25b. How old is this thing?
Still happening in 14w25b.
Affects 14w26c
I just tested if
MC-46579still occurs, noticed this one aswell. Both Bugs can "stack", so misoriented Items stick out of the middle of your arm ^^Oh and I haven't seen this one here yet, shooting arrows out of the middle of your arm...
Fixed, but my test array of floating levers still is there until I BUD it xD