In Beta build 2, upon loading a pre created superflat world in creative, will crash the game.
My device: Samsung Galaxy grand prime
Linked issues
is duplicated by
relates to
Attachments
Comments


This seems to be indirectly related to grass paths and carpets, since walking on them seems to trigger the crashes and crash repeatedly when loading the world

I beg to differ, my device has crashed upon loading a world with no carpets or paths whatsoever.

I beg to differ, my device has crashed upon loading a world with no carpets or paths whatsoever.

Since seeing the "relates to" MCPE-13902 I changed back to the Steve skin and haven't had any crashes.

Since seeing the "relates to" MCPE-13902 I changed back to the Steve skin and haven't had any crashes.

The world I have is pre-created and I crash when I walk past chickens and sheeps are close together.
For some reason when I turn I my render distance all the way down, the crashing has stopped.

The world I have is pre-created and I crash when I walk past chickens and sheeps are close together.
For some reason when I turn I my render distance all the way down, the crashing has stopped.

One thing for sure: it doesn't crash all the time and repeated attempts usually open it (3 is usually the magic number here).
Crashing usually happens around the main core of the map (pre-0.90 terrain)

Looks like it's affecting 0.14.1

I am also experiencing crash issues severe enough as to prevent the game being played. I am using an iPad Pro 12.9-inch running the latest iOS (9.3.1). My Minecraft version is 0.14.1. Whenever I open an existing world, the instant I move from the initial loading location of the character, the game crashes. I can look around, but any movement in any direction will crash the game. I have rebooted my iPad, reverted back to the default "Steve" skin, and turned multiplayer off, but this does not resolve the issue. In fact, I have noticed that the multiplayer-off setting is not retained and is consistently being turned back on after every crash despite being set prior to loading the world. A quick fix for this issue would be appreciated, since the game is currently unplayable for me.

I am also experiencing crash issues severe enough as to prevent the game being played. I am using an iPad Pro 12.9-inch running the latest iOS (9.3.1). My Minecraft version is 0.14.1. Whenever I open an existing world, the instant I move from the initial loading location of the character, the game crashes. I can look around, but any movement in any direction will crash the game. I have rebooted my iPad, reverted back to the default "Steve" skin, and turned multiplayer off, but this does not resolve the issue. In fact, I have noticed that the multiplayer-off setting is not retained and is consistently being turned back on after every crash despite being set prior to loading the world. A quick fix for this issue would be appreciated, since the game is currently unplayable for me.

I think you have a different crash from what this crash is. The crash for me is when it says "Loading" then crashes to the desktop. It sounds like you are actually getting into the game but can't do anything that involves movement.
What happens, though, if you immediately click to quit the game. That should cause a save. Maybe you would have to throw something away or pick something out of a chest to make a change that forces a save. Just don't move I guess.

I think you have a different crash from what this crash is. The crash for me is when it says "Loading" then crashes to the desktop. It sounds like you are actually getting into the game but can't do anything that involves movement.
What happens, though, if you immediately click to quit the game. That should cause a save. Maybe you would have to throw something away or pick something out of a chest to make a change that forces a save. Just don't move I guess.

Thank you for the advice about forcing a save. To be honest, I was getting so frustrated I hadn't thought of trying that. I, unfortunately, got angry and deleted the world that was causing the problem and have not yet created a new one, but when the issue recurs (which I am sure it will) I will try your suggestion.
I hadn't planned on reporting my issue here, however other crash reports that were more in line with what I had been experiencing were being redirected here with the ubiquitous, "this issue is duplicated by...". I'm not sure if this report is being used as the poster child for all crash related issues, or if someone got a little overzealous with the copy/paste. I have had the game crash several times while attempting to load. Basically it hits the splash screen for a split second then tosses me back out to the home screen. Did it nine times in a row, once, but I haven't had that problem since I reverted back to the default Steve skin. I'll keep an eye out for that little piece of fun, too.
Thanks again for the tip!

Thank you for the advice about forcing a save. To be honest, I was getting so frustrated I hadn't thought of trying that. I, unfortunately, got angry and deleted the world that was causing the problem and have not yet created a new one, but when the issue recurs (which I am sure it will) I will try your suggestion.
I hadn't planned on reporting my issue here, however other crash reports that were more in line with what I had been experiencing were being redirected here with the ubiquitous, "this issue is duplicated by...". I'm not sure if this report is being used as the poster child for all crash related issues, or if someone got a little overzealous with the copy/paste. I have had the game crash several times while attempting to load. Basically it hits the splash screen for a split second then tosses me back out to the home screen. Did it nine times in a row, once, but I haven't had that problem since I reverted back to the default Steve skin. I'll keep an eye out for that little piece of fun, too.
Thanks again for the tip!

I am using iPad Air IOS 9.2.1 Minecraft PE 0.14.1 in survival mode. I have been working in a world that I created. Everything works fine for several days. Then when I touch the name of the world to logon, the game crashes and I tossed out to the home screen. No part of the world is opened. I've had this happen on several worlds that I have created over the last few weeks. If I keep trying to open the same world, it eventually works and I can get in and play. It has not crashed while I have been in the world. I've been using the same skin for several months. I even turned the iPad off and restarted it and still have the problem.

Yes what Nancy Vieth says happened to me too. I was so happy that this was fixed and I did play my old game several times to fix things and now all the sudden nada! Game crashes and kicks you out to main screen, meanwhile on background game looks like sill running. Its really messed up! (iPad Air iOS 9.3.1)

Yes what Nancy Vieth says happened to me too. I was so happy that this was fixed and I did play my old game several times to fix things and now all the sudden nada! Game crashes and kicks you out to main screen, meanwhile on background game looks like sill running. Its really messed up! (iPad Air iOS 9.3.1)

This happens up to 6 times when opening a world in the 0.15 beta

This happens up to 6 times when opening a world in the 0.15 beta

It appears when I load my world it crashes once, and then the second time it loads, my animals in my animal farm spawn outside of the building they are held in (sometimes they spawn inside my house nearby). I'm also using 0.15.0. This has never happened to me in previous versions.

It appears when I load my world it crashes once, and then the second time it loads, my animals in my animal farm spawn outside of the building they are held in (sometimes they spawn inside my house nearby). I'm also using 0.15.0. This has never happened to me in previous versions.

Please respond and add the current version if you can reproduce this issue.

Please respond and add the current version if you can reproduce this issue.
This ticket has been resolved as 'Cannot Reproduce' as it has not been updated recently (1 year+)
This ticket has been resolved as 'Cannot Reproduce' as it has not been updated recently (1 year+)