World generating in stripped parts
Some of the big trees in the Jungle biome are invisible, with an sort of wierd stripe pattern. When you try to go through the invisible trees you get a little spazzy and it might be pretty annoying.
Edit: The tree pattern keeps going.
Edit2: (Edit again, sorry for doing this) This does also apply to blocks like tall grass, I'm not sure to what more. And the invisible blocks also gets revealed when they recieve an block update.
Environment
Java Version 7 Update 9
Linked Issues
is duplicated by101
MC-5713Textures probably not loadedDuplicateMC-5751Buggy nether forrestres spawningDuplicateMC-5757Floating/Invisible CactusDuplicateMC-5772Heavy chunk generation bugDuplicateMC-5791biomesDuplicateMC-5841unrenderd snowDuplicateMC-5866Bands of ice/snow in ice plains biomeDuplicateMC-586913w01a Invisable Mineshaft Glitch/BugDuplicateMC-5870Parts of Nether Fortresses spawn invisible and trap the playerDuplicateMC-5892Placing redstone torch change block it's placed onDuplicateMC-5910I made a world to test out the snapshot on and I spawned in a snow biome and there was only snow in in rows of 8 and 8 block gaps of dirt.DuplicateMC-5972Minecraft world generation problemsDuplicateMC-5981RenderingDuplicateMC-6009Problem with generation of biome jungleDuplicateMC-6014Invisible blocks while flying in creativeDuplicateMC-6033Abandoned mineshafts and ore's not renderingDuplicateMC-6064World GernarationDuplicateMC-6082invisible block world generationDuplicateMC-6116Biome IssuesDuplicateMC-6123The landscape is glitchy.DuplicateMC-6138Biome Placement TilingDuplicateMC-6178Swamp Land Invisible TreesDuplicateMC-6190Biome SripsDuplicateMC-6191terrain generation is really messed upDuplicateMC-6203Some trees only generate half.DuplicateMC-6222Stone bricks chunk generating through overworld end portalsDuplicateMC-6235Unrendered spots, biomes, trees (NOT UNRENDERED CHUNKS)DuplicateMC-6255stripesDuplicateMC-6273Villages not generated correctlyDuplicateMC-6276tree bugsDuplicateMC-6288snow doesnt display properlyDuplicateMC-6323Trees being but off by chunk boundariesDuplicateMC-6337 Clusters of blocks are seen as another block or not seen at all.DuplicateMC-6340Invisible mob barriersDuplicateMC-6350random forcefields?DuplicateMC-6352It's an odd world gen bugDuplicateMC-6378Strange world spawningDuplicateMC-6381cactusDuplicateMC-6395stuck in the jungleDuplicateMC-6413Snow and ice generation creates a pattern of stripes in the game where snow and ice appear and don't appear.DuplicateMC-6434Bug with trees forming with half of the tree missingDuplicateMC-6441Invisible floor/ceiling in CreativeDuplicateMC-6499Some cacti are invisibleDuplicateMC-6554Glitched BlocksDuplicateMC-6561The snow biome (or maybe others to) dont end until i get striped biomes.DuplicateMC-6568Invisible Fire?DuplicateMC-6581Block Changes Type when struckDuplicateMC-6599Wrong map generationDuplicateMC-6628Fire Fails to Render Clientside in NetherDuplicateMC-6635Invisible Terrain GlitchDuplicateMC-6645Default World Type Terrain Generation Tree BugDuplicateMC-6662Invisible TreesDuplicateMC-6689The block aren't loaded, as in the videoDuplicateMC-6769Stripy extremehills and snowyhillsDuplicateMC-6787Village generation bugDuplicateMC-6799Blocks are invisible in some places, you cannot walk/fly through them, but placing a block in their position creates the block intended there.DuplicateMC-6812minecraft village blocks not loadDuplicateMC-6839Blocks are invisibleDuplicateMC-6874Villages are not rendering properlyDuplicateMC-6885World is not Rendering CorrectlyDuplicateMC-6893Snow generation bug in Taiga biome.DuplicateMC-6944Tree render bugDuplicateMC-6991what on earthDuplicateMC-7012Invisible blocks and odd chunk generationDuplicateMC-7060Smooth stone changes to dirt if Dispenser is placedDuplicateMC-7061Weird World GenerationDuplicateMC-7076Nether Fortress - Right Click Modifies TerrainDuplicateMC-7090World generation SnowDuplicateMC-7116A BIG error with terrain generation in the snow biomes.DuplicateMC-7140Transparent trees!DuplicateMC-7182Generating biomes, trees and structure are brokenDuplicateMC-7188Villages all messed upDuplicateMC-7189Created a new map and there are 8 wide sections spanning different lengths of the map that are messed up. The biomes change and your player glitches when falling into it from flying.DuplicateMC-7193Block (such as stone or grass, but not limited to) changes when entity is placed on it.DuplicateMC-7212World generation bug - blocks above surface not visible in strips (ie shown, not shown, shown)DuplicateMC-7215Ores and dirt displayed as stone when tunneling.DuplicateMC-7226Invisible entity damage in desert biomeDuplicateMC-7233Chunk ErrorsDuplicateMC-7237Minecraft world generation glitchDuplicateMC-7279World gen bug (stripes)DuplicateMC-7286Trees and Plants above ground not rendering but still causing collisions DuplicateMC-7300Snow comes in stripesDuplicateMC-7309Strips of world not loading properlyDuplicateMC-7352I was placing quartz down in some Extreme Hills, and when I updated block, they would be replaced with water & air. I took some screenshots, quit & logged back in. When I got back, I discovered I had been building on top of a lake that hadn't generated.DuplicateMC-7354World Generation render failsDuplicateMC-7357Trees in newly generated world are not rendered.DuplicateMC-7358Blocks in newly generated chunks are displayed with a different texture temporarillyDuplicateMC-7369Weird chunk renderingDuplicateMC-742913w02b world generate issuesDuplicateMC-7439Invisible and unbreakable blocks.I realy need help It's in 13w02a.DuplicateMC-7456Fire doesn't render in new chunksDuplicateMC-7526Bad End-world generationDuplicateMC-7535Strips of chunks have invisible objectsDuplicateMC-7537Minecraft doesn't generate plants (like trees, cactus, grass) wellDuplicateMC-7558Multiplayer Nether Quartz texture issueDuplicateMC-7575Snow Biomes buggyDuplicateMC-7610jerky movementDuplicateMC-7611Chunk UpdatesDuplicateMC-7613Invisible cactusDuplicateMC-7617When Generating new terrain some blocks are invisibleDuplicateMC-7754chunk errorDuplicateAttachments28
Created Issue:
Invisible trees
Some of the big trees in the Jungle biome are invisible, with an sort of wierd stripe pattern. When you try to go through the invisible trees you get a little spazzy and it might be pretty annoying.
Environment
Java Version 7 Update 9
Attachments1
Some of the big trees in the Jungle biome are invisible, with an sort of wierd stripe pattern. When you try to go through the invisible trees you get a little spazzy and it might be pretty annoying.
Edit: The tree pattern keeps going.
Some of the big trees in the Jungle biome are invisible, with an sort of wierd stripe pattern. When you try to go through the invisible trees you get a little spazzy and it might be pretty annoying.
Edit: The tree pattern keeps going.
Edit2: (Edit again, sorry for doing this) This does also apply to blocks like tall grass, I'm not sure to what more.
Some of the big trees in the Jungle biome are invisible, with an sort of wierd stripe pattern. When you try to go through the invisible trees you get a little spazzy and it might be pretty annoying.
Edit: The tree pattern keeps going.
Edit2: (Edit again, sorry for doing this) This does also apply to blocks like tall grass, I'm not sure to what more. And the invisible blocks also gets revealed when they recieve an block update.
is duplicated by
is duplicated by
is duplicated by
Invisible treesWorld generating in stripped parts
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Still happens in 13w02a, very annoying. My question is how is this even possible...
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
[Mojang] Nathan Adamsis duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
relates to
Despite the resolution, this still isn't fixed. I just got it in 13w017a, singleplayer. This isn't even a matter of phantom unpopulated terrain that returns on world reload - the blocks are literally missing. I even observed a fissure in ice gradually repair itself.
This can be a rather problematic bug, as it means chunks like this are also devoid of ores. Over time, snow will fall, ice will re-form, and endermen will proliferate cacti - on a server, a player may spend hours stripmining and encounter no ores whatsoever in one of these regions, even after it seems to be natural terrain aboveground.
relates to
is duplicated by
relates to
is duplicated by
Duplicate of MC-5737.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
19th duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
20th duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
22nd duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
Yet another duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
@Anon Ymus
- The stone blocks which are visible at the right of the first screenshot
- Since reloading the world solves the problem I don't think it could help. At the beginning right after the bug I tried looking in a external viewer such as minecraft X-Ray and it showed the world normally.
- In fact it IS the
MC-5737bug as seen with the village not generating correctly, as if the "stone chunk" was part of the non structured building chunks (EDIT: saw the mail of duplicate flag for this JIRA)
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
In fact 26th duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
27th duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
28th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
29th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
30th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
31st duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
32nd duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 40% of tickets are being closed as duplicate.
35th duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
37th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
40th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
41st duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of: MC-5737 - Please use the search function to see if your bug has already been submitted.
Currently over 45% of tickets are being closed as duplicate.
Duplicate of: MC-5737 - Please use the search function to see if your bug has already been submitted.
Currently over 45% of tickets are being closed as duplicate.
44th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of: MC-5737 - Please use the search function to see if your bug has already been submitted.
Currently over 45% of tickets are being closed as duplicate.
Duplicate of: MC-5737 - Please use the search function to see if your bug has already been submitted.
Currently over 45% of tickets are being closed as duplicate.
Duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of MC-5737. Please check before posting in the future.
55th duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of MC-5737. Please check before posting in the future.
Duplicate of MC-5737. Please check before posting in the future.
Duplicate of MC-5737. Please check before posting in the future.
Duplicate of MC-5737. Please check before posting in the future.
57th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
58th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
60th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
61st duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
62nd duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
65th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
66th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
67th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
68th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
69th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of MC-5737. Please use the search function to check before posting in the future.
71st duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
I recall a report like this a bit
As much as I like this bug, I admit
Searching's quite fun
And not what you've done
Thus I declare this a duplicate
(MC-5737)
First of all, it clearly is generating in stripped parts. The bug extends to all structures (see MC-5737) and has not been marked as fixed.
73rd duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
79th duplicate of MC-5737 , please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
77th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
Duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 42% of tickets are being closed as duplicate.
79th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 45% of tickets are being closed as duplicate.
80th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 45% of tickets are being closed as duplicate.
83rd duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 45% of tickets are being closed as duplicate.
Duplicate of: MC-5737 - Please use the search function to see if your bug has already been submitted.
Currently over 45% of tickets are being closed as duplicate.
Duplicate of: MC-5737 - Please use the search function to see if your bug has already been submitted.
Currently over 45% of tickets are being closed as duplicate.
87th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 45% of tickets are being closed as duplicate.
88th duplicate of MC-5737, please use the search function to see if your bug has already been submitted. Currently over 45% of tickets are being closed as duplicate.
Or perhaps MC-5737, which is already fixed in recent snapshots.
EDIT: on a closer look, in MC-5737 the stripes are longer without switching the row; this one has obvious change, so could be two worlds made at same height, and that MC-315.
EDIT2: on even closer look, some of the screenshots on MC-5737 do show e.g. changes in the stripe direction. Hard to say which one is the reason for the shown issue.
Following the steps I was able to reproduce the occasional reports of MC-5737 still not beeing fixed. But these should be kept separated since they are reproduced differently.
This may not be relevant, but confirmed for versions dating as far back as 1.3.2 - I've had the bug in the past, but figured it was just a one-time quirk. Yes, I re-loaded the world as I was flying around (inevitably generating chunks just as I reloaded), and the glitch was permanent (whereas MC-5737 is apparently client-side with unglitched server-side terrain?).
I even observed the chunks back then, curious as to why they hadn't populated - in MCedit, they were not marked for population, indicating that the game unmarked them without actually populating them. I've never heard of half-populated chunks, but the screenshots seem to contain doubly-populated chunks - it seems "unmark chunk for population" and "populate chunk" aren't atomic actions with regards to saving chunks, but "populate chunk" on its own is atomic with regards to chunk saving? I find it odd that both "accidentally leave unpopulated" and "accidentally populate twice" are possible, although that may not quite be what's happening in the screenshots.
This is different from the tree issue shown in MC-5737
What I expected to happen was trees generate with whole trunks
I saw a tree near my spawn point with its top half missing
With reference to attachment.
Regenerated in a creative mode version. Same tree weirdness, but top half of tree generated appears to be slightly longer by a bit.
Not confirmed if same weirdness occurs in other areas, seeds etc.
(No idea how my second screenshot so derp)
Also fails to generate snow and villages properly.
Note that this bug existed much earlier, compare for example
MC-3787. But with the current snapshot it seems to be increasingly common.Made a clearer summary.
Snow, ice, trees generated in half-chunkwide stripes; with coordinated and seed. Version 13w01a.
My question is if you have preloaded chunks, will they be effected or just newly generated chunks?
It still happens in 13w01b. See the half trees in the screenshot.
I have this same problem but I have only seen it once in a snow biome. It seems to only be in the new chunks I have loaded.
Update: I saved/Ouit then logged back into the world and it was gone.
@Daniel You're right. When I quit an reload the chunk is normal.
I've created a new world and it happened again. Either there is something wrong during the generation process or the render engine have a problem with the world display after the world creation.
It also happens with Nether Fortresses and Strongholds.
same problem here with the Jungle biomes
Attached a picture of the stripes changing direction.
Added two more pictures. A village before and after I reloaded the game. (2013-01-05_08.10.18.png & 2013-01-05_08.10.56.png)
I had this happen to me in a plains biome. There were strips of snow and over a little farther it had the jungle problem. I noticed that Vines would spawn on sand, in caves, and on the bottom of blocks.
Farlands glitch? I still wonder how adding a couple of blocks to minecraft break the world generation.
Added two screenshots about the problem with strongholds
This has nothing to do with farlands and the world is also generating correctly. The problem seems to be that the server sends the generated world to the client at a state where the land has been generated but the decoration like trees, snow, ice, plants etc. are still missing.
Also, this bug already existed a long time, it has nothing to do with the addition of new blocks.
Seems to me as if this bug gets worse as you generate more land judging by my world and also when water generates in these strings they aren't affected by block updates and I can stand on them.
EDIT: it seems with the strings of chunks, if there's meant to be a tree, a block update will bring the block that was meant to be there.
Probably something like that. I had a thing with an invisible floor I couldn't fly through, but I think it was leaves, because I placed a tower of grass to see if it would place, but the first time I placed a grass block, it turned into a leaf block. Does this only happen w/ transparent blocks?
Minecraft 13w01b: When generating new chunks in the Nether. Fortresses are generated partial. After a "Quit and Save world", all is Ok again.
Gaps appear in Nether Fortresses as well and trap players who walk on them. Still stops Lava, though.
I can verify this happening in my Nether (new chunks generated in 13w01b), looks the same as the broken-up fortress in the screenshots. I've specifically avoided generating any new chunks in the Overworld because of this, so I can't comment on that.
Also, my world is in Survival mode, whereas this bug is defined as Creative. Doesn't seem to make a difference.
This has happened with me when I've been in jungle biomes. Of course, the trees appear when I restart Minecraft. Survival, single-player. I seem to have had a problem related to this with cacti as well.
HAppens with trees, snow, willages (but doors remains), desert temples, Nether fortresses, tall grass, and posiibly more.
It is very annoying bug which sometimes renders exploration almost impossible in forest/jungle area.
Confirmed in 13w02a.
Still present in 13w02b.
Same problems about the snapshot, but it will be fixed soon or not.
Just tried in 13w02b. This problem is still present...
I've seen this occurring in all biomes, both server and client versions (13w02b). It seems to effect all generated entities (trees, plants, and weather) but not the "ground" blocks.
Exiting then reentering, causing a redraw corrects the issue, although more can be found once entering a newly loaded chunk.
I've also deleted and re installed MC with no change.
Render glitch
Render strip glitch
If you try to walk on or into the 'invisible' blocks you will be unable to walk through them and you will just bounce slightly.
Just a small observation I wanted to add.
wow, i have seen one of those bugs where its a long line in the woods without trees, but i have not seen so many others. you are really good at finding those bugs!
To summarize: This affects features added on top of the base terrain, for newly-generated chunks. Most likely the server fails to send the proper updates to the client (this includes the server and client parts of singleplayer).
The client doesn't show any awareness of the blocks at all: it doesn't render them; no selection box shows up when aiming at them; changing neighboring blocks doesn't fix the problem; and it lets you walk into them.
The server, however, will warp you back shortly after attempting to walk into a phantom block. It will also send the correct block if you attempt to place a block inside the phantom block (but only that one block).
Reloading the client fixes everything, at least until more fresh chunks are generated.
I have analyzed the problem a little more. I noticed it's always the half of the chunk closest to you (neighboring already-loaded chunks) that is filled correctly. It also appears to be possible for only a quarter of a chunk to fill in a corner. I suspect 16x16 update groups are offset from chunks, which would cause problems when they overlap any unloaded area.
I have now also seen a vertical instance where trees were cut off above Y=80. It's curious that it's a multiple of 16 rather than a multiple of 16 plus 8. But it's probably about as reproducible as pink sheep, so let's focus on the mass of stripes first.
GOD i hate this bug!
i have exactly the same problem sometimes !
The chunk generator doing bad operands.
@tgilliez why are you still commenting on this bug when it says it has been fixed?
Despite the resolution, this still isn't fixed. I just got it in 13w017a, singleplayer. This isn't even a matter of phantom unpopulated terrain that returns on world reload - the blocks are literally missing. I even observed a fissure in ice gradually repair itself.
This can be a rather problematic bug, as it means chunks like this are also devoid of ores. Over time, snow will fall, ice will re-form, and endermen will proliferate cacti - on a server, a player may spend hours stripmining and encounter no ores whatsoever in one of these regions, even after it seems to be natural terrain aboveground.
My seed is -3848194589049324680, at -213, -362
Just generated the world with the seed you provided and it looks fine, see screenshot.
Ah, I figured it wouldn't be something as straightforward as a seed-based bug. I posted my own screenshots; I'm not sure how to make it reproducible if seed is irrelevant. It could be related to the fact that I exited my world (normal save and quit) and reloaded it before further exploring - who knows; those chunks may have been at the edge of my explored terrain, and got marked as Populated before the populator ran. However, I've had this bug in the past without the need for world reloads, just by flying around aimlessly in Creative, so that likely isn't it either.
Snapshot 13w19a - problem still appears
I was able to reproduce the issue by reloading the world during terrain generation. So please vote for
MC-15820since it has different reproduction steps.