mojira.dev

Kristina Herrboldt

Assigned

No issues.

Reported

MCPE-21842 Crops popping up randomly Cannot Reproduce MCPE-18465 Lapis lazuli not generating naturally Cannot Reproduce MCPE-18352 Dropper to hopper crash Duplicate MCPE-18326 Crash if game cannot connect to wifi Duplicate MCPE-18077 New GUI Laggy Duplicate MCPE-17602 Major Lag On Item Movements Duplicate MCPE-17347 Medieval Texture Pack Errors Cannot Reproduce MCPE-16697 Transfer to/from Chest is very slow Duplicate MCPE-16696 Hoppers duplicating items Fixed MCPE-16680 GUI Controls Blank and/or Stop Working Cannot Reproduce MCPE-16671 Custom Skins and Resources Not Working Invalid MCPE-16667 Crashes On Open Duplicate MCPE-16622 Chests Vanishing Cannot Reproduce WEB-388 JIRA Is bad Invalid MCPE-14736 libEGL cache file failed CRC check Cannot Reproduce MCPE-14497 Crashes On Evil Mob Despawn Cannot Reproduce

Comments

The crash is synched with the weather changes, specifically when it starts to rain. Though rejoining the world causes the check to happen again, meaning it doesn't always rain when it happen but it always happens at the time rain starts.

The last crash caused a chunk to become corrupted in my favorite world, and this in turn causes my entire tablet to lock up and freeze. The problem is that I have no idea of these are actually related because MCPE does not put out any debug information at all. Tks bug reporting would be much simpler for you if you at least enabled debug information for testers.

If my tablet gets ruined by this bug Mojang or Microsoft is replacing it.

Confirmed on Lenovo A10.

Logging out of Xbox no longer resolves this issue in 0.17.0.2

In version 0.1 the workaround no longer works. The game will not run at all without active wifi.

You reproduce the issue by creating a new world in 0.17.

The 0.17 beta is experiencing this crash more, and now it can be triggered by dropping items from the hotbar when using the classic UI setting. Unsure if the two are directly related or this is now two bugs causing the same effects.

That's the thing, my device has 2 gig RAM and a quadcore CPU. It's not an old device, nor is it a low end one. Lenovo is on par with the top teir devices.

This crash appears to be linked to the redstone tick updates now. Often redstone (including doors) starts to misbehave just before the crash. Doors opening on their own and redstone getting stuck or unresponsive, then crash and rollback. In 0.16 the link became very apparent for anything that uses doors, buttons, pressure plates, and levers.

Affects Lenovo A10 as well.

Also effects Lenovo A10

This bug is also in the Android version. Lenovo A10 device.

The crash causes more rollback the higher up you build. Building near 128 always rolls back the changes.

I left the beta because of the map zooming issues, and getting no new build for over a week. So I couldn't tell you. Perhaps someone else can please check on it?

Jira is so glitchy it's hard to use it on mobile devices.

Confirmed on Lenovo A10 Android 5.0.1

How am I suppose to know if they are not connected? It's dealing with resource selection. So which is a seperate issue?

What happens after you select a skin.

The resource storefront.

In the texture pack store selection.