[MCPE-14736] libEGL cache file failed CRC check Created: 04/Jun/16  Updated: 21/Aug/17  Resolved: 21/Aug/17

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.15.0 Beta build 1, 0.15.0, 0.15.1 Beta 1
Fix Version/s: None

Type: Bug
Reporter: Kristina Herrboldt
Resolution: Cannot Reproduce Votes: 1
Labels: None

Attachments: PNG File Screenshot_2016-06-19-02-30-33.png    
Confirmation Status: Unconfirmed
Platform: Tablet - Android - Lenovo A8

 Description   

First, my tablet is a Lenovo A10, your list only guess to A8.

This error causes the game to crash, it appears be linked to mobs and trees. The full line in logcat is:

8922 8943 E libEGL: cache file failed CRC check

Everything is up to date, and this error was happening in previous versions as well.



 Comments   
Comment by [Mojang] Mega_Spud (Jay Wells) [ 21/Aug/17 ]

This ticket has been resolved as 'Cannot Reproduce' as it has not been updated recently (1 year+)

Comment by AMAN4700 [ 08/Aug/16 ]

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

Comment by Kristina Herrboldt [ 28/Jun/16 ]

Other than the difference in devices and versions, it appears to be a duplicate, though mine does state a logcat error that others may not know how to check for.

Comment by kaleb418 [ 24/Jun/16 ]

Awaiting input on whether it is a duplicate of that report.

Comment by Kristina Herrboldt [ 24/Jun/16 ]

Yes, that describes it accurately.

Comment by kaleb418 [ 22/Jun/16 ]

Does this issue act like MCPE-12347?

Comment by Kristina Herrboldt [ 22/Jun/16 ]

Both, all versions from 0.14.1, just more prominant in 0.15.*. Also, the player inventory is updated, but chest contents are reset. This can cause duplication or loss of items transfered between a chest and inventory. It also causes mobs to be reset.

Basically, the player status is preserved at the crash, but the chunk changes are not.

Comment by kaleb418 [ 21/Jun/16 ]

Does this issue affect 0.15.0 or 0.15.1 Beta build 1? If so, please respond and update the affects version.

Comment by Kristina Herrboldt [ 21/Jun/16 ]

An example of one of the effects of this bug. Those leaves were desroyed just before a crash, tree is still gone, but this chunk lost all changes.

Comment by Kristina Herrboldt [ 18/Jun/16 ]

Note, the problem did not actually stop. The crashes occurred less frequently right after the update but have become more frequent as time goes on. Clearing the cache does nothing to correct it.

Steps to reproduce: get a Lenovo A10, play for a couple of hours, the crash will happen. The crash is most frequent on easy or above, but still occurs on peaceful.

There is absolutely no apparent pattern, and the issue is in the GL cache usage. Using texture packs increases the frequency of the crash, higher resolution textures cause more frequent crashes.

Comment by Kristina Herrboldt [ 12/Jun/16 ]

The recent build (3) appears to have corrected the crash. The logcat line still shows up though.

Comment by Kristina Herrboldt [ 07/Jun/16 ]

The actual devs need to address this issue, I'd wager that many of the random crashes reported are the exact same thing. Remember that file access on Android is ALWAYS asynchronous, you cannot expect an app to have immediate access to a cache file. You need to rely on RAM more, or just tell the players to deal with lag.

Comment by Kristina Herrboldt [ 06/Jun/16 ]

There are no steps as there is a lot that happens in the game which cannot be seen by the player (me) and no apparent pattern seems to be present. The issue is during updates to chunks, the trigger is unknown and virtually unknowable.

However, the common effects may enlighten the devs:

1. Mob locations when reloading the game after the crash seem bound by the distance to the player in nearby chunks. Meaning they appear to move about the same distance and direction of the player.

2. Often large changes to a build are lost, as if nothing was changed including changes to the original terrain, and the resources used are gone forever. This often shows obvious chunk boundaries of effect.

3. Plant growth seems unredacted by this. Trees, wheat, etc. seem too grow as expected of this glitch occurs. Though trees that were chopped do return to fully grown, sometimes with disastrous results if being chopped at the time of the crash.

4. The players location is unaffected by the crash, you start at the exact location you were when the crash occurs.

5. I've closed all unnecessary apps, but the bug persists, my tablet is shown as "Lenovo TAB 2 A10-70F" It uses a Dolby sound system, standard Android OS, kernel 3.10.61, SDK version 5.0.1

Comment by kaleb418 [ 04/Jun/16 ]

Please add the steps to reproduce the issue if possible.

Generated at Sat Jan 11 15:04:56 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.