Zhuowei Zhang
- zhuowei
- zhuowei
- America/Los_Angeles
- Yes
- No
MCPE-6412MCPE-25225
To reproduce (On Nexus 7 (2012) at least, not sure how to trigger a low memory event on other devices)
- Open Minecraft PE
- Go to Settings
- Skins
- Custom
- When the browser for skins shows up, hit the back button
- Once back in MCPE, hit the Multitask button
Expected:
- MCPE gets placed in background
Actual:- MCPE force-closes with this stack trace: https://gist.github.com/zhuowei/e9a43e30ba268dfdf192
It looks like the low memory handler tried to destroy the LevelRenderer, but since no world has been loaded, the LevelRenderer was null and the destructor segfaulted.
To reproduce (On Nexus 7 (2012) at least, not sure how to trigger a low memory event on other devices)
- Open Minecraft PE
- Go to Settings
- Skins
- Custom
- When the browser for skins shows up, hit the back button
- Once back in MCPE, hit the Multitask button
Expected:
- MCPE gets placed in background
Actual:
- MCPE force-closes with this stack trace: https://gist.github.com/zhuowei/e9a43e30ba268dfdf192
It looks like the low memory handler tried to destroy the LevelRenderer, but since no world has been loaded, the LevelRenderer was null and the destructor segfaulted.
Segfault when low memory event firedSegfault when low memory event fires
To reproduce:
- Place rails
- Place Minecart
- Tap Ride
- Player gets into cart
Expected result: message pops up, saying, "Tap Jump to Exit Minecart"
Actual result: no message is shown
This seems to be a regression from 0.14.1. I can reproduce this both on Nexus 7 2012 on Android 4.4.4 and on Nexus 6P on Android 6.0.1
.To reproduce:
- Place rails
- Place Minecart
- Tap Ride
- Player gets into cart
Expected result: message pops up, saying, "Tap Jump to Exit Minecart"
Actual result: no message is shown
This seems to be a regression from 0.14.1. I can reproduce this both on Nexus 7 2012 on Android 4.4.4 (tested on Realms build 2) and on Nexus 6P on Android 6.0.1 (tested on Realms build 2 and 0.14.2)
"Tap Jump to Exit Minecart" message missing in Realms beta, 0.14.2
Upgrading to Android 8.0.0 causes black screen at startup untildata is clearedUpgrading to Android 8.0.0 causes black screen at startup until ShaderCache2 is deleted
The vibration on block destruction doesn't work for blocks that take time to break in Survival mode.
Tested on a Google/Huawei Nexus 6P with Minecraft 1.6.0.14 (release version) and 1.7.0.3 (beta).
To reproduce:
- Generate a new Survival world.
- Make sure Settings -> Touch -> Destroy Block (Vibrate) is turned on.
- Break some grass, dirt, or stone (tested by breaking with bare hands)
Expected result:
- when the block breaks on screen, the device should vibrate slightly.
Actual result:
- Device does not vibrate.
This only works for blocks that take time to break: tall grass and oxeye daisies both vibrate when destroyed, because they break instantly. In addition, this doesn't happen in Creative mode: all blocks cause vibration when destroyed.
.mcworld files with an ampersand in their name won't import when opened.
To reproduce:
- rename a .mcworld file to "test&case.mcworld"
- select the renamed mcworld file in a file manager, and select Minecraft to start the import
- Minecraft opens
Expected: Minecraft then pops up the "Importing level" banner and imports the .mcworld file
Actual: nothing happens; Minecraft enters the title screen without importing the level.
.mcworld files with an ampersand in their name won't import when opened.
Tested on a Nexus 6P running Android 8.1.
To reproduce:
- rename a .mcworld file to "test&case.mcworld"
- select the renamed mcworld file in a file manager, and select Minecraft to start the import
- Minecraft opens
Expected: Minecraft then pops up the "Importing level" banner and imports the .mcworld file
Actual: nothing happens; Minecraft enters the title screen without importing the level.
Since the closing as "Awaiting Response" was automated and no moderators had updated the affected versions since the comment by Zhuowei Zhang, this bug was closed even though it had already been confirmed for 0.17.0.1 Reopening & updating the affected versions...
Zhuowei Zhang, sorry for taking so long to respond... please do test on the Nexus 7 to see if this issue is still occurring in 1.2.5.52 and/or 1.2.6.2.
Ah, well, it is fixed in the latest release anyways.
I can reproduce as well - Android 4.0, Toshiba Thrive, MCPE 0.6.1 without any mods patched from Google Play.
Steps to reproduce:
Steps to avoid the problem:
Confirmed on Nexus 7 running stock firmware as well.
Confirmed, and made a patch that fixes it for Android. It's available on my mod thread.
The source of the bug is embarrassingly simple: Mojang typed a 0 instead of a 1.
Block.TNT.postBreak(world, i, j, k, 0);
Since they based the fire behaviour on Minecraft 1.5
When they should've typed
Block.TNT.postBreak(world, i, j, k, 1);
Which is Desktop Edition 1.6 and above's code, used to port TNT.
(method names are from Bukkit on the desktop edition)
The relevant function is in FireTile::checkBurn.
Mojang fail level: 0... I mean 1.
Confirmed Android 0.7.1, Asus Nexus 7, Android 4.2.2, and made a patch that fixes it for Android. It's available on my mod thread.
The source of the bug is embarrassingly simple: Mojang typed a 0 instead of a 1.
They based the fire behaviour on Minecraft 1.5, which had the line of code
Block.TNT.postBreak(world, i, j, k, 0);
However, TNT was ported from a later Desktop release, which meant that the line of code was supposed to be
Block.TNT.postBreak(world, i, j, k, 1);
(method names are from Bukkit on the desktop edition)
The relevant function is in FireTile::checkBurn.
Mojang fail level: 0... I mean 1.
Confirmed in 0.7.2 (Android from Google Play, same Nexus 7 as before)
Looks like GameMode::startDestroyBlock isn't being called; that function is responsible for calling Level::extinguishFire to put out the fire when you punch a block in Survival.
Still affects 0.17.0 alpha build 1 when using Left Handed mode: I'm on a Nexus 6P running Android 7.0.
Can confirm: running 1.0.5.0 on Nexus 6P/Android 7.1.1.
Can confirm: Minecraft PE 1.0.5.0, Android 7.1.1 on Nexus 6P, Gboard 6.1.71.149620197-arm64-v8a
Can confirm: Android 7.1.2, Nexus 6P, 1.2.0.18.
I can't reproduce 1 and 3, but I can reproduce a crash when cancelling an Xbox Live signin. Android 7.1.2, Nexus 6P, Minecraft 1.2.0.18
Can confirm: Minecraft PE 1.12.0.18, Android 8.0.0, Nexus 6P
Manually deleting the cache/minecraftpe/ShaderCache2 folder also fixes the problem. It seems that Minecraft PE doesn't invalidate the shader cache on OS upgrade.
@SuperGeniusZeb I can't trigger it on 1.2.0b22 on a Nexus 6P anymore, but maybe that device is too fast; I can check on the Nexus 7 again if you want.
Still reproducing on 1.2.0.25.
Still reproducing on 1.2.0 full release. (why...)
Still reproducing on 1.2.0 release.
This seems to be fixed in 1.6.0 release (Nexus 6P, Android 8.1.0): worlds opened on 1.6.0 shows non-glitched screenshots; worlds that were never opened on 1.6.0 still had glitched previews.
Still occurs on 1.9.0.0 Beta.
Can reproduce on Google/Huawei Nexus 6P, Android 8.1, Minecraft 1.9.0.3 beta.
My symptoms are the same as
MCPE-39428: sometimes, when entering a world, all blocks are black (in inventory, in hand, and in the world). Items and mobs render normally. This happens about once in 20 times.Exiting and reopening the world fixes the issue. Backgrounding and then resuming Minecraft also fixes the issue.