This crash still happens if you summon a boat as a passenger of a boat that is a passenger of an entity.
Steps to reproduce
1. Insert the following Command into a CommandBlock and trigger it:
/summon creeper ~ ~2 ~ {Passengers:[{id:boat,Passengers:[{id:boat}]}]}Happens also when you specify the boat material type:
/summon creeper ~ ~2 ~ {Passengers:[{id:"boat",Type:"oak",Passengers:[{id:"boat",Type:"oak"}]}]}2. Result
My world gets unresponsive, when I open the GUI of the CommandBlock, it shows up empty.
It's as if I'm in a ghost mode, but I can make screenshots still though, successfully.
See screenshot of the unresponsive CommandBlock GUI (buttons are not clickable).I seem to be able to place blocks, but when I relog into the world after I forcequit, they are not there.
Sadly I can not force a crash with F3-C, and I don't get any crash report when I forcequit, but in my Launcher it says this:
[08:03:32 ERROR]: Game ended with bad state (exit code -805306369)
[08:03:32 INFO]: Ignoring visibility rule and showing launcher due to a game crash
Reproducable 100% with that command for everyone, to confirm it.
Interestingly something possibly new I noticed - not sure if it never occurred in the older MC versions with only 1 boat as passenger or I just overlooked it:
When I summoned the ridden entity, crashed, and re-log into the world, the entity and its passengers are not in the world anymore.
If I recall correctly, that's different from before (with 1 boat as passenger), but I don't know if that really matters.
Thank you, regards,
Meri
Linked issues
is duplicated by 4
Attachments
Comments 19
Exit code -805306369 is Out of Memory, see http://hopper.minecraft.net/help/exit-code/code-805306369/?preview=1
Redo the screenshots with debug screen enabled.
I just noticed I accidentially used the entityname "Boat" with capital B instead of "boat".
If I use the wrong name "Boat", it summons the stacked entity as shown, and the crash happens.
If I try to summon the stacked entity with "boat", with small letter b, it only summons the Villager, as you can see here.
Same goes for e.g. dark_oak_boat.
The give-command for these boats work though.
As requested, screenshot with F3 on, uses ~3GB of 8GB.
i don't know why it gives out the wrong exitcode then, if I assigned enough RAM?
This bug seems to be back again. Now it requires 2 boat passengers to freeze the game. Same result (server side frozen). Here's the command I used:
/summon Pig ~ ~10 ~ {Passengers:[{id:Boat,Passengers:[{id:Boat}]}]}
@unknown Good find! I never tested an additional boat.
Confirmed, game gets unresponsive like before, I don't get any crash log, just this in the Launcher:
[11:09:33 ERROR]: Game ended with bad state (exit code -805306369)
[11:09:33 INFO]: Ignoring visibility rule and showing launcher due to a game crash
Please reopen bugpost and I'll adjust the "how to reproduce" step etc.
If I shall make a new one, please tell me to do so!
Clearer explanation: CommandBlock was used to summon the stacked entity;
after summoning it, if you open its GUI, it appears to be empty.
If you insert the same (or another) command into it, the buttons are STILL NOT clickable; it's not because the commandline seems to be empty that the buttons are not clickable.