Andreas

I am having the same issue as well.  One on my original  mojang account, and my migrated MS account

I could trace the issue back to Wayland. Somehow Gnome switched from Xorg to Wayland and I had no issues otherwise. This results is:

Xorg: Works as intended.

Wayland: Lagging as described above.

The issue could have something to do with Wayland, hope this helps anybody in the future.

Thank you for your hint. But it does not resolve the issue. I switched to Java 8 and the bug is still present. (See second screenshot.)

Using notifyAll() and wait() with a short timeout is probably the way to go (or use semaphores instead of timeouts). Technically this is not hard to realize, somebody just has to do it. But one would need the complete, compilable sourcecode to fix this 🙂

Minecraft is not FOSS after all :/

This probably doesn't help much, but since I want to test this server, I can't let the CPU idle around on 100% on a core all the time.

First time editing a bytecode, I've modified my 19w06a snapshot by replacing the call of Thread.yield() to Thread.sleep(1) just for testing (as suggested in a previous comment). Funny thing, it isn't pretty and the average tick time rose by like 50% on the system, but the cpu usage of the process dropped to like 3%-4% . Don't know if the performance is way down now, but at least I can let the server run for further testing.

It seems another person has gotten almost the same error message as me. Their screenshot can be seen. I hope you can make this report valid, if that person runs Vanilla Minecraft.

It's also worth mentioning that Optifine should have no impact on the chat. All that it modifies, is rendering, as far as I'm concerned. I also wonder how Optifine works compared to Vanilla. It gives many more fps, and gives options for different ways of rendering textures. A little strange a plugin can raise my fps from 15 to 43, and give a more stable game.

Got the game working again, by removing the selected resource pack from the resource pack folder, launching the game, readding the resource pack, and reselecting it. I still have no idea why the error occured in the first place.

I want to add some info about my testing devices: lg g4, galaxy note 8010 and lenovo tablet. Different Android Versions Marshmallow, Kitkat and Jellybean.

I can reproduce this issue over and over with current version of Minecraft PE 0.15.4.0
It seems to happen when the engine tries to write to leveldb.
I tried to move the files (all inside db-folder) to newly created world and it crashes as well...

Hope this can be solved or somehow fixed. Is there a way to clone the worlds data into a new database?

Same here for Minecraft PE 0.15.1 on a world thats 262MB large. World renders for a short time, I'm able to move a bit but then it shuts down with the message "world is corrupted and can't be saved"
Please ask me for more information if wanted.

Many thanks in advance for fixing that.
Seems to be a writing problem in leveldb.

I also have a question, and that is if the lightning on water is a bug, or that the water isn't meant to have smooth lightning?

Sorry, but I did use the search function, and I didn't find these reports.

Sorry, I forgot to mention that some shadows completely dissapear, for example as I "fix" the shadow errors in picture "2016-06-04_17.34.25". (Picture number 2). I suppose you understand that "fix" doesn't mean a fix, but a temporarily removal of the poblems until the chunks are reloaded. Also, I can tell you that the shadow errors in picture "2016-06-02_08.18.11" (picture number 1) constantly kept changing during the process of building the platform. Surprisingly, these are now fixed. (I also made two 4x4 holes on each of the edges of the platform).

Sorry if there are typos such as capitol letters at the start of words in the middle of sentences. The auto corrector makes these.

When switching from nether to overworld even the nether portal is not rendered.

Even not rendered redstone circuits work just fine. There is an automatic chicken farm nearby, thats why there are so many entities.

Turning off advancedOpengl fixes the problem (and the framerate slightly better)

Forced crash report attached: crash-2014-07-12_12.34.22-client.txt and screenshot 2014-07-12_12.32.53.png

Had the same issue, also with an iron door. Stack traces look exactly the same as in the original report.

No i was play in redstone ready than i blow a tnt when in the snapshot when
i change to 1.7.9 i se it was stone not sandstone
On May 27, 2014 11:28 PM, "[Mod] Mustek (JIRA)" <[email protected]> wrote:

> [Mod] Mustek<https://bugs.mojang.com/secure/ViewProfile.jspa?name=mustek>
> resolved an issue as Cannot Reproduce
>
> Can't reproduce. There was probably stone beneath the sandstone that got
> blown up as well.
> Minecraft <https://bugs.mojang.com/browse/MC> / [image: Bug]<https://bugs.mojang.com/browse/MC-55927>
> MC-55927 <https://bugs.mojang.com/browse/MC-55927> when sandstone
> desrtoyed bt TNT/creeper/minecraft with TNT makes a stone not a sandstone<https://bugs.mojang.com/browse/MC-55927> Change
> By: [Mod] Mustek<https://bugs.mojang.com/secure/ViewProfile.jspa?name=mustek> Resolution:
> Cannot Reproduce Status: Open Resolved [image: Add Comment]
> <https://bugs.mojang.com/browse/MC-55927#add-comment> Add Comment<https://bugs.mojang.com/browse/MC-55927#add-comment> This message was sent by Atlassian JIRA
> (v6.1.6#6162-sha1:7af547c) [image: Atlassian logo]
>

Ups sorry :/

Well, We can't say you did not spend any time on this...

Well done. Thanks.

Andreas

Regards,

Andreas Niederegger

Same with us.
It's a read/write issue. Once I assigned administrator rights the problem was resolved

Good luck to all.