Lag/Massive resource usage

We are experiencing this as well. We had our world hosted on a Realm and it was lagging horribly for everyone all the time, does not appear to be player event driven for us. We thought it was network lag because it was effecting everybody so we downloaded the realm and tried playing locally. For the network players they experience laggy response but for the host it is complete UI freezes and extremely high CPU utilization. It appears to be periodically triggered as it will spike for awhile then clear up then start again. There are about 7 threads starting from ucrtbase.dll!o__realloc_base+0x20 that take up all available CPU when the hanging starts. I have an 8 core CPU and it's taking over all 8 cores. I've removed all resource packs and it hasn't had any impact.

We are experiencing this as well. We had our world hosted on a Realm and it was lagging horribly for everyone all the time, does not appear to be player event driven for us. We thought it was network lag because it was effecting everybody so we downloaded the realm and tried playing locally. For the network players they experience laggy response but for the host it is complete UI freezes and extremely high CPU utilization. It appears to be periodically triggered as it will spike for awhile then clear up then start again. There are about 7 threads starting from ucrtbase.dll!o__realloc_base+0x20 that take up all available CPU when the hanging starts. I have an 8 core CPU and it's taking over all 8 cores. I've removed all resource packs and it hasn't had any impact.

We are experiencing this as well. We had our world hosted on a Realm and it was lagging horribly for everyone all the time, does not appear to be player event driven for us. We thought it was network lag because it was effecting everybody so we downloaded the realm and tried playing locally. For the network players they experience laggy response but for the host it is complete UI freezes and extremely high CPU utilization. It appears to be periodically triggered as it will spike for awhile then clear up then start again. There are about 7 threads starting from ucrtbase.dll!o__realloc_base+0x20 that take up all available CPU when the hanging starts. I have an 8 core CPU and it's taking over all 8 cores. I've removed all resource packs and it hasn't had any impact.

We are experiencing this as well. We had our world hosted on a Realm and it was lagging horribly for everyone all the time, does not appear to be player event driven for us. We thought it was network lag because it was effecting everybody so we downloaded the realm and tried playing locally. For the network players they experience laggy response but for the host it is complete UI freezes and extremely high CPU utilization. It appears to be periodically triggered as it will spike for awhile then clear up then start again. There are about 7 threads starting from ucrtbase.dll!o__realloc_base+0x20 that take up all available CPU when the hanging starts. I have an 8 core CPU and it's taking over all 8 cores. I've removed all resource packs and it hasn't had any impact.

Still affecting worlds in 1.1.3.1

Still affecting worlds in 1.1.3.1

Still affecting worlds in 1.1.3.1

Still affecting worlds in 1.1.3.1

This may have something to do with how fast the player moves in a given direction, when my world was corrupted I had been riding a horse, I restored that world from a backup, climbed on a new horse and am now experiencing this issue again.

My best bet is that the speed of player movement may cause too many updates in quick succession for the database/storage device to handle potentially resulting in "fragmentation" of database files, especially when traversing new areas where chunks have not yet been generated, as I was.

If this is the case a method be added to the world settings to "defragment" or sanity check the '*.ldb' files in the same way you can run a compact and repair on an Access database to free the deleted records and correct varying levels of fragmentation/corruption may help the user mitigate the issues this causes as not everyone has access to backups or is willing to loose a "days work".

This may have something to do with how fast the player moves in a given direction, when my world was corrupted I had been riding a horse, I restored that world from a backup, climbed on a new horse and am now experiencing this issue again.

My best bet is that the speed of player movement may cause too many updates in quick succession for the database/storage device to handle potentially resulting in "fragmentation" of database files, especially when traversing new areas where chunks have not yet been generated, as I was.

If this is the case a method be added to the world settings to "defragment" or sanity check the '*.ldb' files in the same way you can run a compact and repair on an Access database to free the deleted records and correct varying levels of fragmentation/corruption may help the user mitigate the issues this causes as not everyone has access to backups or is willing to loose a "days work".

This may have something to do with how fast the player moves in a given direction, when my world was corrupted I had been riding a horse, I restored that world from a backup, climbed on a new horse and am now experiencing this issue again.

My best bet is that the speed of player movement may cause too many updates in quick succession for the database/storage device to handle potentially resulting in "fragmentation" of database files, especially when traversing new areas where chunks have not yet been generated, as I was.

If this is the case a method be added to the world settings to "defragment" or sanity check the '*.ldb' files in the same way you can run a compact and repair on an Access database to free the deleted records and correct varying levels of fragmentation/corruption may help the user mitigate the issues this causes as not everyone has access to backups or is willing to loose a "days work".

This may have something to do with how fast the player moves in a given direction, when my world was corrupted I had been riding a horse, I restored that world from a backup, climbed on a new horse and am now experiencing this issue again.

My best bet is that the speed of player movement may cause too many updates in quick succession for the database/storage device to handle potentially resulting in "fragmentation" of database files, especially when traversing new areas where chunks have not yet been generated, as I was.

If this is the case a method be added to the world settings to "defragment" or sanity check the '*.ldb' files in the same way you can run a compact and repair on an Access database to free the deleted records and correct varying levels of fragmentation/corruption may help the user mitigate the issues this causes as not everyone has access to backups or is willing to loose a "days work".

The lag certainly feels like .ldb processing, but to a much greater degree than normal. I agree that travelling large distances quickly might be a root cause, as this happened on one of my survival worlds when I travelled to and from a woodland mansion.

The lag certainly feels like .ldb processing, but to a much greater degree than normal. I agree that travelling large distances quickly might be a root cause, as this happened on one of my survival worlds when I travelled to and from a woodland mansion.

The lag certainly feels like .ldb processing, but to a much greater degree than normal. I agree that travelling large distances quickly might be a root cause, as this happened on one of my survival worlds when I travelled to and from a woodland mansion.

The lag certainly feels like .ldb processing, but to a much greater degree than normal. I agree that travelling large distances quickly might be a root cause, as this happened on one of my survival worlds when I travelled to and from a woodland mansion.

I have the exact same problem. Whilst it certainly becomes more apparent and grossly worse as overland travel is done via horse or running, it is still a prominent occurrence just staying within a small area. Reducing the render distance does not have a noticeable effect for me, and I also have an 8 Core machine.

Simply standing still is enough to make it cause soaring CPU Usage. Oddly enough, my girlfriend's computer which often connects via LAN to me, does not suffer from the same lagging issue, and she has an Intel CPU one step down from mine, with otherwise equivalent hardware. Though, she does often have invisible, unloaded chunks when my CPU is soaring from it. When I first started the world, it ran fine. In fact, I had an even larger one I was running just a few months ago on the same machine and it never experienced this lag. But this world has progressively gotten worse and has more or less just plateaued at this level of lagginess. Sometimes it borders on unplayable, other times it's fine. I don't experience this issue with any other application or game.

I have the exact same problem. Whilst it certainly becomes more apparent and grossly worse as overland travel is done via horse or running, it is still a prominent occurrence just staying within a small area. Reducing the render distance does not have a noticeable effect for me, and I also have an 8 Core machine.

Simply standing still is enough to make it cause soaring CPU Usage. Oddly enough, my girlfriend's computer which often connects via LAN to me, does not suffer from the same lagging issue, and she has an Intel CPU one step down from mine, with otherwise equivalent hardware. Though, she does often have invisible, unloaded chunks when my CPU is soaring from it. When I first started the world, it ran fine. In fact, I had an even larger one I was running just a few months ago on the same machine and it never experienced this lag. But this world has progressively gotten worse and has more or less just plateaued at this level of lagginess. Sometimes it borders on unplayable, other times it's fine. I don't experience this issue with any other application or game.

I have the exact same problem. Whilst it certainly becomes more apparent and grossly worse as overland travel is done via horse or running, it is still a prominent occurrence just staying within a small area. Reducing the render distance does not have a noticeable effect for me, and I also have an 8 Core machine.

Simply standing still is enough to make it cause soaring CPU Usage. Oddly enough, my girlfriend's computer which often connects via LAN to me, does not suffer from the same lagging issue, and she has an Intel CPU one step down from mine, with otherwise equivalent hardware. Though, she does often have invisible, unloaded chunks when my CPU is soaring from it. When I first started the world, it ran fine. In fact, I had an even larger one I was running just a few months ago on the same machine and it never experienced this lag. But this world has progressively gotten worse and has more or less just plateaued at this level of lagginess. Sometimes it borders on unplayable, other times it's fine. I don't experience this issue with any other application or game.

I have the exact same problem. Whilst it certainly becomes more apparent and grossly worse as overland travel is done via horse or running, it is still a prominent occurrence just staying within a small area. Reducing the render distance does not have a noticeable effect for me, and I also have an 8 Core machine.

Simply standing still is enough to make it cause soaring CPU Usage. Oddly enough, my girlfriend's computer which often connects via LAN to me, does not suffer from the same lagging issue, and she has an Intel CPU one step down from mine, with otherwise equivalent hardware. Though, she does often have invisible, unloaded chunks when my CPU is soaring from it. When I first started the world, it ran fine. In fact, I had an even larger one I was running just a few months ago on the same machine and it never experienced this lag. But this world has progressively gotten worse and has more or less just plateaued at this level of lagginess. Sometimes it borders on unplayable, other times it's fine. I don't experience this issue with any other application or game.

Unfortunately if you are now experiencing CPU spikes like this when standing still there is no current way to repair you map files.
If you have a backup of that map the best you can do is restore it and avoid long distance and fast traveling.

If you get the occasional CPU spike when moving to a new area stop everything and just wait for it to pass, this appears to mitigate the currently irreversible damage to map files.
It would be wise to export a copy of your world if you are not currently experiencing non-stop latency.

Your graphical settings will have no effect on this.

Unfortunately if you are now experiencing CPU spikes like this when standing still there is no current way to repair you map files.
If you have a backup of that map the best you can do is restore it and avoid long distance and fast traveling.

If you get the occasional CPU spike when moving to a new area stop everything and just wait for it to pass, this appears to mitigate the currently irreversible damage to map files.
It would be wise to export a copy of your world if you are not currently experiencing non-stop latency.

Your graphical settings will have no effect on this.

Unfortunately if you are now experiencing CPU spikes like this when standing still there is no current way to repair you map files.
If you have a backup of that map the best you can do is restore it and avoid long distance and fast traveling.

If you get the occasional CPU spike when moving to a new area stop everything and just wait for it to pass, this appears to mitigate the currently irreversible damage to map files.
It would be wise to export a copy of your world if you are not currently experiencing non-stop latency.

Your graphical settings will have no effect on this.

Unfortunately if you are now experiencing CPU spikes like this when standing still there is no current way to repair you map files.
If you have a backup of that map the best you can do is restore it and avoid long distance and fast traveling.

If you get the occasional CPU spike when moving to a new area stop everything and just wait for it to pass, this appears to mitigate the currently irreversible damage to map files.
It would be wise to export a copy of your world if you are not currently experiencing non-stop latency.

Your graphical settings will have no effect on this.

Our realm has been experiencing extreme lag and frequent realm crashes since the 1.1 update. It seems to be worse when players are going through a nether or end portal, in another dimension or trying to connect to the game. Chunks do not load, pressure plates and buttons fail to work, chests cannot be opened, dropped items cannot be picked up from the ground, the entire realm grinds to a halt often resulting in a realm crash. Reducing render distance and other graphic settings don't make any difference. After the 1.1 update, we did travel 10,000 blocks from spawn to find one of the new woodland mansions. We have also traveled great distances in the end in search of end cities. It seems like that should not cause serious issues as these generated structures are intended to be rare and require distant travel to reach.

Our realm has been experiencing extreme lag and frequent realm crashes since the 1.1 update. It seems to be worse when players are going through a nether or end portal, in another dimension or trying to connect to the game. Chunks do not load, pressure plates and buttons fail to work, chests cannot be opened, dropped items cannot be picked up from the ground, the entire realm grinds to a halt often resulting in a realm crash. Reducing render distance and other graphic settings don't make any difference. After the 1.1 update, we did travel 10,000 blocks from spawn to find one of the new woodland mansions. We have also traveled great distances in the end in search of end cities. It seems like that should not cause serious issues as these generated structures are intended to be rare and require distant travel to reach.

Our realm has been experiencing extreme lag and frequent realm crashes since the 1.1 update. It seems to be worse when players are going through a nether or end portal, in another dimension or trying to connect to the game. Chunks do not load, pressure plates and buttons fail to work, chests cannot be opened, dropped items cannot be picked up from the ground, the entire realm grinds to a halt often resulting in a realm crash. Reducing render distance and other graphic settings don't make any difference. After the 1.1 update, we did travel 10,000 blocks from spawn to find one of the new woodland mansions. We have also traveled great distances in the end in search of end cities. It seems like that should not cause serious issues as these generated structures are intended to be rare and require distant travel to reach.

Our realm has been experiencing extreme lag and frequent realm crashes since the 1.1 update. It seems to be worse when players are going through a nether or end portal, in another dimension or trying to connect to the game. Chunks do not load, pressure plates and buttons fail to work, chests cannot be opened, dropped items cannot be picked up from the ground, the entire realm grinds to a halt often resulting in a realm crash. Reducing render distance and other graphic settings don't make any difference. After the 1.1 update, we did travel 10,000 blocks from spawn to find one of the new woodland mansions. We have also traveled great distances in the end in search of end cities. It seems like that should not cause serious issues as these generated structures are intended to be rare and require distant travel to reach.

I can now confirm beyond much doubt that hardware has little to no effect on this issue. I upgraded my hardware a couple of days ago and there has been no noticeable reduction of CPU consumption on my Minecraft world.

However, unlike before decreasing render distance to 5 does (sometimes) impact how long the CPU spikes last.
Same story though, moving any distance causes CPU usage to spike to 100% for approx 15 seconds (With render distance 5) and using portals to the nether has a 50/50 chance of crashing the game.

I can now confirm beyond much doubt that hardware has little to no effect on this issue. I upgraded my hardware a couple of days ago and there has been no noticeable reduction of CPU consumption on my Minecraft world.

However, unlike before decreasing render distance to 5 does (sometimes) impact how long the CPU spikes last.
Same story though, moving any distance causes CPU usage to spike to 100% for approx 15 seconds (With render distance 5) and using portals to the nether has a 50/50 chance of crashing the game.

I can now confirm beyond much doubt that hardware has little to no effect on this issue. I upgraded my hardware a couple of days ago and there has been no noticeable reduction of CPU consumption on my Minecraft world.

However, unlike before decreasing render distance to 5 does (sometimes) impact how long the CPU spikes last.
Same story though, moving any distance causes CPU usage to spike to 100% for approx 15 seconds (With render distance 5) and using portals to the nether has a 50/50 chance of crashing the game.

I can now confirm beyond much doubt that hardware has little to no effect on this issue. I upgraded my hardware a couple of days ago and there has been no noticeable reduction of CPU consumption on my Minecraft world.

However, unlike before decreasing render distance to 5 does (sometimes) impact how long the CPU spikes last.
Same story though, moving any distance causes CPU usage to spike to 100% for approx 15 seconds (With render distance 5) and using portals to the nether has a 50/50 chance of crashing the game.

I'm having the same problem on 1.1.5 on Windows 10, with similar hardware (i7-4770k, 16GB RAM, GeForce GTX 780 and Samsung EVO SSD)

Sometimes it freezes for a couple of minutes when going to/from the nether, before even showing the loading screen, and it can also crash immediately when using a portal.

I'm having the same problem on 1.1.5 on Windows 10, with similar hardware (i7-4770k, 16GB RAM, GeForce GTX 780 and Samsung EVO SSD)

Sometimes it freezes for a couple of minutes when going to/from the nether, before even showing the loading screen, and it can also crash immediately when using a portal.

I'm having the same problem on 1.1.5 on Windows 10, with similar hardware (i7-4770k, 16GB RAM, GeForce GTX 780 and Samsung EVO SSD)

Sometimes it freezes for a couple of minutes when going to/from the nether, before even showing the loading screen, and it can also crash immediately when using a portal.

I'm having the same problem on 1.1.5 on Windows 10, with similar hardware (i7-4770k, 16GB RAM, GeForce GTX 780 and Samsung EVO SSD)

Sometimes it freezes for a couple of minutes when going to/from the nether, before even showing the loading screen, and it can also crash immediately when using a portal.

I have probably the worst PC ever and everything is running smoothly for me on all the version so listed. Are You awareness of anything triggering this extreme CPU usage?

I have probably the worst PC ever and everything is running smoothly for me on all the version so listed. Are You awareness of anything triggering this extreme CPU usage?

I have probably the worst PC ever and everything is running smoothly for me on all the version so listed. Are You awareness of anything triggering this extreme CPU usage?

I have probably the worst PC ever and everything is running smoothly for me on all the version so listed. Are You awareness of anything triggering this extreme CPU usage?

So I made another thread which has now been redirected to this, and I would like to ask if the developers or working on optimizing these issues? Or have they at least heard of it? These issues can ruin the whole Minecraft Experience (although the Marketplace will ruin everything) and I would at least like to know that someone is looking for a fix.

So I made another thread which has now been redirected to this, and I would like to ask if the developers or working on optimizing these issues? Or have they at least heard of it? These issues can ruin the whole Minecraft Experience (although the Marketplace will ruin everything) and I would at least like to know that someone is looking for a fix.

So I made another thread which has now been redirected to this, and I would like to ask if the developers or working on optimizing these issues? Or have they at least heard of it? These issues can ruin the whole Minecraft Experience (although the Marketplace will ruin everything) and I would at least like to know that someone is looking for a fix.

So I made another thread which has now been redirected to this, and I would like to ask if the developers or working on optimizing these issues? Or have they at least heard of it? These issues can ruin the whole Minecraft Experience (although the Marketplace will ruin everything) and I would at least like to know that someone is looking for a fix.

Same problem here! I have a 175 MB survival world (single player). When I play, the CPU usage go to 100 % without motivation. This cause a continuos stuttering, making the videogame impractical. I have a decent hardware and Minecraft Windows 10 Edition is the only game that causes me this problem. I have already reinstalled the game, updated all the drivers (gpu included). Nothing changed.

Same problem here! I have a 175 MB survival world (single player). When I play, the CPU usage go to 100 % without motivation. This cause a continuos stuttering, making the videogame impractical. I have a decent hardware and Minecraft Windows 10 Edition is the only game that causes me this problem. I have already reinstalled the game, updated all the drivers (gpu included). Nothing changed.

Same problem here! I have a 175 MB survival world (single player). When I play, the CPU usage go to 100 % without motivation. This cause a continuos stuttering, making the videogame impractical. I have a decent hardware and Minecraft Windows 10 Edition is the only game that causes me this problem. I have already reinstalled the game, updated all the drivers (gpu included). Nothing changed.

Same problem here! I have a 175 MB survival world (single player). When I play, the CPU usage go to 100 % without motivation. This cause a continuos stuttering, making the videogame impractical. I have a decent hardware and Minecraft Windows 10 Edition is the only game that causes me this problem. I have already reinstalled the game, updated all the drivers (gpu included). Nothing changed.

Having the same issue, and my world is slowly becoming unplayable. Why is this still not being looked at? This is a major, game-breaking bug.

Having the same issue, and my world is slowly becoming unplayable. Why is this still not being looked at? This is a major, game-breaking bug.

Having the same issue, and my world is slowly becoming unplayable. Why is this still not being looked at? This is a major, game-breaking bug.

Having the same issue, and my world is slowly becoming unplayable. Why is this still not being looked at? This is a major, game-breaking bug.

Start making backups of your worlds, currently there is no known way to revert the damage to your world files without Mojangs developers creating a fix.
At least if you take a backup you can salvage some playability.

Start making backups of your worlds, currently there is no known way to revert the damage to your world files without Mojangs developers creating a fix.
At least if you take a backup you can salvage some playability.

Start making backups of your worlds, currently there is no known way to revert the damage to your world files without Mojangs developers creating a fix.
At least if you take a backup you can salvage some playability.

Start making backups of your worlds, currently there is no known way to revert the damage to your world files without Mojangs developers creating a fix.
At least if you take a backup you can salvage some playability.

I make regular backups, but that doesn't really help the problem of being unable to expand our world. If I have to keep reverting to a backup, what's the point in doing anything at all? It's certainly good advice to always keep a backup, though! I may just run the world on an old laptop as the host since it's only the host that experiences CPU spiking; my partner doesn't experience any lag on the same world, only me since I'm the host.

I make regular backups, but that doesn't really help the problem of being unable to expand our world. If I have to keep reverting to a backup, what's the point in doing anything at all? It's certainly good advice to always keep a backup, though! I may just run the world on an old laptop as the host since it's only the host that experiences CPU spiking; my partner doesn't experience any lag on the same world, only me since I'm the host.

I make regular backups, but that doesn't really help the problem of being unable to expand our world. If I have to keep reverting to a backup, what's the point in doing anything at all? It's certainly good advice to always keep a backup, though! I may just run the world on an old laptop as the host since it's only the host that experiences CPU spiking; my partner doesn't experience any lag on the same world, only me since I'm the host.

I make regular backups, but that doesn't really help the problem of being unable to expand our world. If I have to keep reverting to a backup, what's the point in doing anything at all? It's certainly good advice to always keep a backup, though! I may just run the world on an old laptop as the host since it's only the host that experiences CPU spiking; my partner doesn't experience any lag on the same world, only me since I'm the host.

The issue is caused by a number of known faults in the leveldb file system, Minecraft PE/Win 10/Console uses this to store game data with, one of the most common of these faults is reading/writing to RAM too quickly for the filesystem. Now while leveldb a very fast and exceptionally lightweight database structure it is seriously prone to corruption, Mojang has created their own version of this database for Minecraft but they have clearly not been able to resolve the issues which lead to corruption.

In theory one way to correct a damaged database would be to re-write the files however this would result in more lost data due to corrupted segments needing to be ignored entirely, re-written data would therefore be incomplete and need to be regenerated which would probably cause chunks to be completely different, in other words you house might end up being half destroyed and replaced with a random tree.

Things you can try to mitigate database corruption are:

1. Avoid traveling at any speed other than normal walking, the faster you move the more the game has to generate and save to disk.

2. Take regular "breaks" while traveling (don't just go in one directory for a solid hour, stop every 10 minutes or so to ensure the game has time to process).

3. Avoid making large and quick, consecutive changes to the map such as mining a 1x1 column to bedrock and filling it with TNT.

4. Decrease your render distance.

It is worth remembering that Minecraft both reads and writes to the map files at the same time, the larger your render distance the more chunks needs to be loaded and unloaded while you move, this is just added stress to the database which we now know is not reliable enough to handle these changes.

The issue is caused by a number of known faults in the leveldb file system, Minecraft PE/Win 10/Console uses this to store game data with, one of the most common of these faults is reading/writing to RAM too quickly for the filesystem. Now while leveldb a very fast and exceptionally lightweight database structure it is seriously prone to corruption, Mojang has created their own version of this database for Minecraft but they have clearly not been able to resolve the issues which lead to corruption.

In theory one way to correct a damaged database would be to re-write the files however this would result in more lost data due to corrupted segments needing to be ignored entirely, re-written data would therefore be incomplete and need to be regenerated which would probably cause chunks to be completely different, in other words you house might end up being half destroyed and replaced with a random tree.

Things you can try to mitigate database corruption are:

1. Avoid traveling at any speed other than normal walking, the faster you move the more the game has to generate and save to disk.

2. Take regular "breaks" while traveling (don't just go in one directory for a solid hour, stop every 10 minutes or so to ensure the game has time to process).

3. Avoid making large and quick, consecutive changes to the map such as mining a 1x1 column to bedrock and filling it with TNT.

4. Decrease your render distance.

It is worth remembering that Minecraft both reads and writes to the map files at the same time, the larger your render distance the more chunks needs to be loaded and unloaded while you move, this is just added stress to the database which we now know is not reliable enough to handle these changes.

The issue is caused by a number of known faults in the leveldb file system, Minecraft PE/Win 10/Console uses this to store game data with, one of the most common of these faults is reading/writing to RAM too quickly for the filesystem. Now while leveldb a very fast and exceptionally lightweight database structure it is seriously prone to corruption, Mojang has created their own version of this database for Minecraft but they have clearly not been able to resolve the issues which lead to corruption.

In theory one way to correct a damaged database would be to re-write the files however this would result in more lost data due to corrupted segments needing to be ignored entirely, re-written data would therefore be incomplete and need to be regenerated which would probably cause chunks to be completely different, in other words you house might end up being half destroyed and replaced with a random tree.

Things you can try to mitigate database corruption are:

1. Avoid traveling at any speed other than normal walking, the faster you move the more the game has to generate and save to disk.

2. Take regular "breaks" while traveling (don't just go in one directory for a solid hour, stop every 10 minutes or so to ensure the game has time to process).

3. Avoid making large and quick, consecutive changes to the map such as mining a 1x1 column to bedrock and filling it with TNT.

4. Decrease your render distance.

It is worth remembering that Minecraft both reads and writes to the map files at the same time, the larger your render distance the more chunks needs to be loaded and unloaded while you move, this is just added stress to the database which we now know is not reliable enough to handle these changes.

The issue is caused by a number of known faults in the leveldb file system, Minecraft PE/Win 10/Console uses this to store game data with, one of the most common of these faults is reading/writing to RAM too quickly for the filesystem. Now while leveldb a very fast and exceptionally lightweight database structure it is seriously prone to corruption, Mojang has created their own version of this database for Minecraft but they have clearly not been able to resolve the issues which lead to corruption.

In theory one way to correct a damaged database would be to re-write the files however this would result in more lost data due to corrupted segments needing to be ignored entirely, re-written data would therefore be incomplete and need to be regenerated which would probably cause chunks to be completely different, in other words you house might end up being half destroyed and replaced with a random tree.

Things you can try to mitigate database corruption are:

1. Avoid traveling at any speed other than normal walking, the faster you move the more the game has to generate and save to disk.

2. Take regular "breaks" while traveling (don't just go in one directory for a solid hour, stop every 10 minutes or so to ensure the game has time to process).

3. Avoid making large and quick, consecutive changes to the map such as mining a 1x1 column to bedrock and filling it with TNT.

4. Decrease your render distance.

It is worth remembering that Minecraft both reads and writes to the map files at the same time, the larger your render distance the more chunks needs to be loaded and unloaded while you move, this is just added stress to the database which we now know is not reliable enough to handle these changes.

All great points! I'm hoping that the unified nature of the Better Together update might entail some improvements to the DB system. And to be fair, I've been running at a 56 chunk render distance... Hate to scale it back as that's been a major part of how I explore my world, but it's better than ruining everything I suppose. Here's to hoping 1.2 fixes this even if this Jira ticket has gone ignored by Mojang... I'm sure this issue affects several aspects of performance.

All great points! I'm hoping that the unified nature of the Better Together update might entail some improvements to the DB system. And to be fair, I've been running at a 56 chunk render distance... Hate to scale it back as that's been a major part of how I explore my world, but it's better than ruining everything I suppose. Here's to hoping 1.2 fixes this even if this Jira ticket has gone ignored by Mojang... I'm sure this issue affects several aspects of performance.

All great points! I'm hoping that the unified nature of the Better Together update might entail some improvements to the DB system. And to be fair, I've been running at a 56 chunk render distance... Hate to scale it back as that's been a major part of how I explore my world, but it's better than ruining everything I suppose. Here's to hoping 1.2 fixes this even if this Jira ticket has gone ignored by Mojang... I'm sure this issue affects several aspects of performance.

All great points! I'm hoping that the unified nature of the Better Together update might entail some improvements to the DB system. And to be fair, I've been running at a 56 chunk render distance... Hate to scale it back as that's been a major part of how I explore my world, but it's better than ruining everything I suppose. Here's to hoping 1.2 fixes this even if this Jira ticket has gone ignored by Mojang... I'm sure this issue affects several aspects of performance.

Thanks for all of the input so far. We are very much aware of this issue and progress is being made. Many players that suffered with this problem on their worlds have had this issue solved in the 1.2 beta.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki

Thanks for all of the input so far. We are very much aware of this issue and progress is being made. Many players that suffered with this problem on their worlds have had this issue solved in the 1.2 beta.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki

Thanks for all of the input so far. We are very much aware of this issue and progress is being made. Many players that suffered with this problem on their worlds have had this issue solved in the 1.2 beta.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki

Thanks for all of the input so far. We are very much aware of this issue and progress is being made. Many players that suffered with this problem on their worlds have had this issue solved in the 1.2 beta.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki

Yes, I'm having the same problem(s). And have been referred to this post which does appear quite similar. For me it is the mother of all problems at in my opinion it renders the whole game useless. I am now on my 3rd survival world which has now become unplayable.
As I am an electronics engineer I am very grateful to hear the explanations above from Terry. Many Thanks Terry. It is a relief to have some of the mechanics explained. I find it helps somewhat.
I would also love to hear if possible more explanation on how minecraft gathers and uses it's data as we move around a world. As I can't quite understand why it should be that the data shifting / storing problem becomes worse and worse as the map gets bigger. Almost exponentially.
For example I can create a grid of 9 large maps in a new world and move quite freely around them as fast and for as long as I want to. If i keep on creating more and more maps things begin to slow down. But my logic concludes that this should not be the case. That other maps created much earlier and further away should not required for use, therefore are stored away until a time when I become closer to them. Then they can be called for and the others put away. Therefore the amount of data required should be pretty constant and the data read and writing would be the same and should shelve off at some point and things should remain stable. As although I am travelling through several maps, the amount of graphical information i can see at any one time is always pretty much the same. But this does'nt seem to be the case. It's as if minecraft needs always to take into consideration all or some of all the map data regardless of the direction or area one is at. Feel free to explain......

Yes, I'm having the same problem(s). And have been referred to this post which does appear quite similar. For me it is the mother of all problems at in my opinion it renders the whole game useless. I am now on my 3rd survival world which has now become unplayable.
As I am an electronics engineer I am very grateful to hear the explanations above from Terry. Many Thanks Terry. It is a relief to have some of the mechanics explained. I find it helps somewhat.
I would also love to hear if possible more explanation on how minecraft gathers and uses it's data as we move around a world. As I can't quite understand why it should be that the data shifting / storing problem becomes worse and worse as the map gets bigger. Almost exponentially.
For example I can create a grid of 9 large maps in a new world and move quite freely around them as fast and for as long as I want to. If i keep on creating more and more maps things begin to slow down. But my logic concludes that this should not be the case. That other maps created much earlier and further away should not required for use, therefore are stored away until a time when I become closer to them. Then they can be called for and the others put away. Therefore the amount of data required should be pretty constant and the data read and writing would be the same and should shelve off at some point and things should remain stable. As although I am travelling through several maps, the amount of graphical information i can see at any one time is always pretty much the same. But this does'nt seem to be the case. It's as if minecraft needs always to take into consideration all or some of all the map data regardless of the direction or area one is at. Feel free to explain......

Yes, I'm having the same problem(s). And have been referred to this post which does appear quite similar. For me it is the mother of all problems at in my opinion it renders the whole game useless. I am now on my 3rd survival world which has now become unplayable.
As I am an electronics engineer I am very grateful to hear the explanations above from Terry. Many Thanks Terry. It is a relief to have some of the mechanics explained. I find it helps somewhat.
I would also love to hear if possible more explanation on how minecraft gathers and uses it's data as we move around a world. As I can't quite understand why it should be that the data shifting / storing problem becomes worse and worse as the map gets bigger. Almost exponentially.
For example I can create a grid of 9 large maps in a new world and move quite freely around them as fast and for as long as I want to. If i keep on creating more and more maps things begin to slow down. But my logic concludes that this should not be the case. That other maps created much earlier and further away should not required for use, therefore are stored away until a time when I become closer to them. Then they can be called for and the others put away. Therefore the amount of data required should be pretty constant and the data read and writing would be the same and should shelve off at some point and things should remain stable. As although I am travelling through several maps, the amount of graphical information i can see at any one time is always pretty much the same. But this does'nt seem to be the case. It's as if minecraft needs always to take into consideration all or some of all the map data regardless of the direction or area one is at. Feel free to explain......

Yes, I'm having the same problem(s). And have been referred to this post which does appear quite similar. For me it is the mother of all problems at in my opinion it renders the whole game useless. I am now on my 3rd survival world which has now become unplayable.
As I am an electronics engineer I am very grateful to hear the explanations above from Terry. Many Thanks Terry. It is a relief to have some of the mechanics explained. I find it helps somewhat.
I would also love to hear if possible more explanation on how minecraft gathers and uses it's data as we move around a world. As I can't quite understand why it should be that the data shifting / storing problem becomes worse and worse as the map gets bigger. Almost exponentially.
For example I can create a grid of 9 large maps in a new world and move quite freely around them as fast and for as long as I want to. If i keep on creating more and more maps things begin to slow down. But my logic concludes that this should not be the case. That other maps created much earlier and further away should not required for use, therefore are stored away until a time when I become closer to them. Then they can be called for and the others put away. Therefore the amount of data required should be pretty constant and the data read and writing would be the same and should shelve off at some point and things should remain stable. As although I am travelling through several maps, the amount of graphical information i can see at any one time is always pretty much the same. But this does'nt seem to be the case. It's as if minecraft needs always to take into consideration all or some of all the map data regardless of the direction or area one is at. Feel free to explain......

Unfortunately I cannot do justice to the explanation of how LevelDB works nor it's use in Minecraft.

What I do know is that it's not at all surprising to me to see hiccups like this when reading and writing millions of records concurrently.

I mean lets assume your render distance is 16, this would create a grid 32 (+1) chunks squared the +1 is due to the fact that chunks are rendered based on what blocks should be visible not just when you enter/exit a chunk.
Oh and each chunk, that's a 16*16*256 set of blocks 16*16 square that is 256 blocks high for a total of 65,536 blocks.

Every time you move, that 32 (+1) squared set of chunks gets moved.

Doing the math on this 32 (+ 1) squared grid results in 67,108,864 to 71,368,704 blocks being loaded in memory at any given moment.

If you only move in one direction, let's say North, you'll be generating 2,162,688 (a row of 32 (+1) chunks) new blocks 15 chunks North of you all while saving changes to the 2,162,688 blocks that are no longer needed in memory 16 blocks South of you.
Want to move diagonally? That'll be 4,128,768 to 4,259,840 new blocks in your given direction and the same again needing to be saved in the opposite direction.

To make matters worse, all these blocks are relative so they have to take into consideration the neighbouring chunk's blocks to complete cave systems and alike.
Add on top of this mobs and items and your looking at some serious data.

I'll be pleasantly surprised if in fact Mojang does find a working solution to avoid corruption using the same database format.

Unfortunately I cannot do justice to the explanation of how LevelDB works nor it's use in Minecraft.

What I do know is that it's not at all surprising to me to see hiccups like this when reading and writing millions of records concurrently.

I mean lets assume your render distance is 16, this would create a grid 32 (+1) chunks squared the +1 is due to the fact that chunks are rendered based on what blocks should be visible not just when you enter/exit a chunk.
Oh and each chunk, that's a 16*16*256 set of blocks 16*16 square that is 256 blocks high for a total of 65,536 blocks.

Every time you move, that 32 (+1) squared set of chunks gets moved.

Doing the math on this 32 (+ 1) squared grid results in 67,108,864 to 71,368,704 blocks being loaded in memory at any given moment.

If you only move in one direction, let's say North, you'll be generating 2,162,688 (a row of 32 (+1) chunks) new blocks 15 chunks North of you all while saving changes to the 2,162,688 blocks that are no longer needed in memory 16 blocks South of you.
Want to move diagonally? That'll be 4,128,768 to 4,259,840 new blocks in your given direction and the same again needing to be saved in the opposite direction.

To make matters worse, all these blocks are relative so they have to take into consideration the neighbouring chunk's blocks to complete cave systems and alike.
Add on top of this mobs and items and your looking at some serious data.

I'll be pleasantly surprised if in fact Mojang does find a working solution to avoid corruption using the same database format.

Unfortunately I cannot do justice to the explanation of how LevelDB works nor it's use in Minecraft.

What I do know is that it's not at all surprising to me to see hiccups like this when reading and writing millions of records concurrently.

I mean lets assume your render distance is 16, this would create a grid 32 (+1) chunks squared the +1 is due to the fact that chunks are rendered based on what blocks should be visible not just when you enter/exit a chunk.
Oh and each chunk, that's a 16*16*256 set of blocks 16*16 square that is 256 blocks high for a total of 65,536 blocks.

Every time you move, that 32 (+1) squared set of chunks gets moved.

Doing the math on this 32 (+ 1) squared grid results in 67,108,864 to 71,368,704 blocks being loaded in memory at any given moment.

If you only move in one direction, let's say North, you'll be generating 2,162,688 (a row of 32 (+1) chunks) new blocks 15 chunks North of you all while saving changes to the 2,162,688 blocks that are no longer needed in memory 16 blocks South of you.
Want to move diagonally? That'll be 4,128,768 to 4,259,840 new blocks in your given direction and the same again needing to be saved in the opposite direction.

To make matters worse, all these blocks are relative so they have to take into consideration the neighbouring chunk's blocks to complete cave systems and alike.
Add on top of this mobs and items and your looking at some serious data.

I'll be pleasantly surprised if in fact Mojang does find a working solution to avoid corruption using the same database format.

Unfortunately I cannot do justice to the explanation of how LevelDB works nor it's use in Minecraft.

What I do know is that it's not at all surprising to me to see hiccups like this when reading and writing millions of records concurrently.

I mean lets assume your render distance is 16, this would create a grid 32 (+1) chunks squared the +1 is due to the fact that chunks are rendered based on what blocks should be visible not just when you enter/exit a chunk.
Oh and each chunk, that's a 16*16*256 set of blocks 16*16 square that is 256 blocks high for a total of 65,536 blocks.

Every time you move, that 32 (+1) squared set of chunks gets moved.

Doing the math on this 32 (+ 1) squared grid results in 67,108,864 to 71,368,704 blocks being loaded in memory at any given moment.

If you only move in one direction, let's say North, you'll be generating 2,162,688 (a row of 32 (+1) chunks) new blocks 15 chunks North of you all while saving changes to the 2,162,688 blocks that are no longer needed in memory 16 blocks South of you.
Want to move diagonally? That'll be 4,128,768 to 4,259,840 new blocks in your given direction and the same again needing to be saved in the opposite direction.

To make matters worse, all these blocks are relative so they have to take into consideration the neighbouring chunk's blocks to complete cave systems and alike.
Add on top of this mobs and items and your looking at some serious data.

I'll be pleasantly surprised if in fact Mojang does find a working solution to avoid corruption using the same database format.

I've updated to the 1.2 beta and am happy to report that I'm no longer having this issue!

I've updated to the 1.2 beta and am happy to report that I'm no longer having this issue!

I've updated to the 1.2 beta and am happy to report that I'm no longer having this issue!

I've updated to the 1.2 beta and am happy to report that I'm no longer having this issue!

Hi Richard Craig,
That sounds promising!
Could you tell me if it's possible to use ones existing worlds (pre 1.2 beta worlds) on the 1.2 beta version? And if so will they show up as usual at the beginning or does one have to search for the old files and mess around etc.?
Many Thanks

Richard A

Hi Richard Craig,
That sounds promising!
Could you tell me if it's possible to use ones existing worlds (pre 1.2 beta worlds) on the 1.2 beta version? And if so will they show up as usual at the beginning or does one have to search for the old files and mess around etc.?
Many Thanks

Richard A

Hi Richard Craig,
That sounds promising!
Could you tell me if it's possible to use ones existing worlds (pre 1.2 beta worlds) on the 1.2 beta version? And if so will they show up as usual at the beginning or does one have to search for the old files and mess around etc.?
Many Thanks

Richard A

Hi Richard Craig,
That sounds promising!
Could you tell me if it's possible to use ones existing worlds (pre 1.2 beta worlds) on the 1.2 beta version? And if so will they show up as usual at the beginning or does one have to search for the old files and mess around etc.?
Many Thanks

Richard A

On Windows 10 and Android, it works like any other update and loads your previous worlds just fine, no hunting required.

On Windows 10 and Android, it works like any other update and loads your previous worlds just fine, no hunting required.

On Windows 10 and Android, it works like any other update and loads your previous worlds just fine, no hunting required.

On Windows 10 and Android, it works like any other update and loads your previous worlds just fine, no hunting required.

Thanks again Terry.

Your explanations are very thorough and thought provoking.

Richard A

Thanks again Terry.

Your explanations are very thorough and thought provoking.

Richard A

Thanks again Terry.

Your explanations are very thorough and thought provoking.

Richard A

Thanks again Terry.

Your explanations are very thorough and thought provoking.

Richard A

Thanks for the prompt reply Richard. I may yet give it a try...

Richard A

Thanks for the prompt reply Richard. I may yet give it a try...

Richard A

Thanks for the prompt reply Richard. I may yet give it a try...

Richard A

Thanks for the prompt reply Richard. I may yet give it a try...

Richard A

Tried to access 1.2 beta on xbox insider hub but it won't show up in the contents page. Boohooo

Tried to access 1.2 beta on xbox insider hub but it won't show up in the contents page. Boohooo

Tried to access 1.2 beta on xbox insider hub but it won't show up in the contents page. Boohooo

Tried to access 1.2 beta on xbox insider hub but it won't show up in the contents page. Boohooo

1.2 seems to have completely fixed these issues for me.

1.2 seems to have completely fixed these issues for me.

1.2 seems to have completely fixed these issues for me.

1.2 seems to have completely fixed these issues for me.

This appears to have fixed issues with maps and movement, however new issues resulting in lag have appeared with regards to the crafting changes (also dragging items across crafting table slots).

Also an issue that was not as prominent before was placing torches while mining. If placed quickly enough it would take a torch from your inventory placing it for a split second before vanishing, since joining the BETA program this is much easier to encounter and also seems to occur when moving and placing torches.

I have also encountered a minor inventory glitch where shift clicking 6 brown mushrooms into a chest with 44 mushrooms, left a "ghost" item in my character inventory and did not update the chest inventory.
This took some persistence to remedy manually dragging the stack from the chest into my inventory until it finally updated the stack, then logging out and back in before moving it back into the chest, to get the correct item count of 50 brown mushrooms I had to repeat the logout/login step again.

The main thing is that the map glitches now appear to be corrected.

This appears to have fixed issues with maps and movement, however new issues resulting in lag have appeared with regards to the crafting changes (also dragging items across crafting table slots).

Also an issue that was not as prominent before was placing torches while mining. If placed quickly enough it would take a torch from your inventory placing it for a split second before vanishing, since joining the BETA program this is much easier to encounter and also seems to occur when moving and placing torches.

I have also encountered a minor inventory glitch where shift clicking 6 brown mushrooms into a chest with 44 mushrooms, left a "ghost" item in my character inventory and did not update the chest inventory.
This took some persistence to remedy manually dragging the stack from the chest into my inventory until it finally updated the stack, then logging out and back in before moving it back into the chest, to get the correct item count of 50 brown mushrooms I had to repeat the logout/login step again.

The main thing is that the map glitches now appear to be corrected.

This appears to have fixed issues with maps and movement, however new issues resulting in lag have appeared with regards to the crafting changes (also dragging items across crafting table slots).

Also an issue that was not as prominent before was placing torches while mining. If placed quickly enough it would take a torch from your inventory placing it for a split second before vanishing, since joining the BETA program this is much easier to encounter and also seems to occur when moving and placing torches.

I have also encountered a minor inventory glitch where shift clicking 6 brown mushrooms into a chest with 44 mushrooms, left a "ghost" item in my character inventory and did not update the chest inventory.
This took some persistence to remedy manually dragging the stack from the chest into my inventory until it finally updated the stack, then logging out and back in before moving it back into the chest, to get the correct item count of 50 brown mushrooms I had to repeat the logout/login step again.

The main thing is that the map glitches now appear to be corrected.

This appears to have fixed issues with maps and movement, however new issues resulting in lag have appeared with regards to the crafting changes (also dragging items across crafting table slots).

Also an issue that was not as prominent before was placing torches while mining. If placed quickly enough it would take a torch from your inventory placing it for a split second before vanishing, since joining the BETA program this is much easier to encounter and also seems to occur when moving and placing torches.

I have also encountered a minor inventory glitch where shift clicking 6 brown mushrooms into a chest with 44 mushrooms, left a "ghost" item in my character inventory and did not update the chest inventory.
This took some persistence to remedy manually dragging the stack from the chest into my inventory until it finally updated the stack, then logging out and back in before moving it back into the chest, to get the correct item count of 50 brown mushrooms I had to repeat the logout/login step again.

The main thing is that the map glitches now appear to be corrected.