14w28a crashes when loading World

same prob. here, render distance does not seem to effect it here either.
the new world i stardet works, apart from a huge amount of lag.
I was just mining dirt when this bad boy showed up:

Minecraft Crash Report ----
// But it works on my machine.

Time: 9/07/14 20:09
Description: Exception ticking world

java.lang.IllegalArgumentException: Cannot get property bcl{name=age, clazz=class java.lang.Integer, values=[0, 1, 2, 3, 4, 5, 6, 7]} as it does not exist!
at bbw.b(SourceFile:91)
at ayt.b(SourceFile:127)
at ayt.c(SourceFile:69)
at ary.b(SourceFile:416)
at qg.h(SourceFile:373)
at qg.c(SourceFile:199)
at net.minecraft.server.MinecraftServer.x(SourceFile:578)
at net.minecraft.server.MinecraftServer.w(SourceFile:510)
at cwg.w(SourceFile:132)
at net.minecraft.server.MinecraftServer.run(SourceFile:426)
at java.lang.Thread.run(Unknown Source)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

– Head –
Stacktrace:
at bbw.b(SourceFile:91)
at ayt.b(SourceFile:127)
at ayt.c(SourceFile:69)
at ary.b(SourceFile:416)
at qg.h(SourceFile:373)
at qg.c(SourceFile:199)

– Affected level –
Details:
Level name: New World
All players: 1 total; [qj['Tjahzi'/152, l='New World', x=-140,05, y=69,00, z=-255,59]]
Chunk stats: ServerChunkCache: 1182 Drop: 0
Level seed: -6998018604335337772
Level generator: ID 00 - default, ver 1. Features enabled: true
Level generator options:
Level spawn location: -252,00,64,00,-92,00 - World: (-252,64,-92), Chunk: (at 4,4,4 in -16,-6; contains blocks -256,0,-96 to -241,255,-81), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
Level time: 3361632 game time, 4081262 day time
Level dimension: 0
Level storage version: 0x04ABD - Anvil
Level weather: Rain time: 141146 (now: false), thunder time: 103533 (now: false)
Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
Stacktrace:
at net.minecraft.server.MinecraftServer.x(SourceFile:578)
at net.minecraft.server.MinecraftServer.w(SourceFile:510)
at cwg.w(SourceFile:132)
at net.minecraft.server.MinecraftServer.run(SourceFile:426)
at java.lang.Thread.run(Unknown Source)

– System Details –
Details:
Minecraft Version: 14w28a
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.6.0_20, Sun Microsystems Inc.
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Sun Microsystems Inc.
Memory: 245901608 bytes (234 MB) / 573833216 bytes (547 MB) up to 954466304 bytes (910 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
Profiler Position: N/A (disabled)
Player Count: 1 / 8; [qj['Tjahzi'/152, l='New World', x=-140,05, y=69,00, z=-255,59]]
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.

Another clue: I have a command block at spawn on my server that automatically does a /spreadplayers for new players. Spawn is very sparse. The area in the spread is also somewhat sparse, typically.

I've seen new players stay connected for 20+ minutes. If this bug is related to specific block ids, apparently those block ids are not naturally present everywhere, thus certain players in unbuilt areas do not cause the crash.

But once an established player logs in, the server crashes.

I am also seeing this bug with a very old world of mine (from 2010) that was last opened with 14w27b. I am still able to open it with 27b. I noticed some people on Reddit mentioning double stone slabs, and I used a ton of them in the part of the world I am working in now. I remember yesterday I had made some of those double stone slabs, and they looked different than ones that had been placed with earlier builds.

Minecraft Crash Report ----
// You're mean.

Time: 7/9/14 12:16 PM
Description: Exception ticking world

java.lang.IllegalArgumentException: Cannot get property bcl{name=age, clazz=class java.lang.Integer, values=[0, 1, 2, 3, 4, 5, 6, 7]} as it does not exist!
at bbw.b(SourceFile:91)
at ayt.b(SourceFile:127)
at ayt.c(SourceFile:69)
at ary.b(SourceFile:416)
at qg.h(SourceFile:373)
at qg.c(SourceFile:199)
at net.minecraft.server.MinecraftServer.x(SourceFile:578)
at net.minecraft.server.MinecraftServer.w(SourceFile:510)
at cwg.w(SourceFile:132)
at net.minecraft.server.MinecraftServer.run(SourceFile:426)
at java.lang.Thread.run(Thread.java:695)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

– Head –
Stacktrace:
at bbw.b(SourceFile:91)
at ayt.b(SourceFile:127)
at ayt.c(SourceFile:69)
at ary.b(SourceFile:416)
at qg.h(SourceFile:373)
at qg.c(SourceFile:199)

– Affected level –
Details:
Level name: Happy Smurf Land
All players: 1 total; [qj['HappySmurfday'/72, l='Happy Smurf Land', x=162.97, y=63.50, z=-120.85]]
Chunk stats: ServerChunkCache: 1064 Drop: 0
Level seed: 109568207
Level generator: ID 00 - default, ver 1. Features enabled: true
Level generator options:
Level spawn location: -120.00,65.00,143.00 - World: (-120,65,143), Chunk: (at 8,4,15 in -8,8; contains blocks -128,0,128 to -113,255,143), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
Level time: 68945162 game time, 76546536 day time
Level dimension: 0
Level storage version: 0x04ABD - Anvil
Level weather: Rain time: 18824 (now: true), thunder time: 24216 (now: false)
Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
Stacktrace:
at net.minecraft.server.MinecraftServer.x(SourceFile:578)
at net.minecraft.server.MinecraftServer.w(SourceFile:510)
at cwg.w(SourceFile:132)
at net.minecraft.server.MinecraftServer.run(SourceFile:426)
at java.lang.Thread.run(Thread.java:695)

– System Details –
Details:
Minecraft Version: 14w28a
Operating System: Mac OS X (x86_64) version 10.9.4
Java Version: 1.6.0_65, Apple Inc.
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Apple Inc.
Memory: 60910600 bytes (58 MB) / 304644096 bytes (290 MB) up to 1069416448 bytes (1019 MB)
JVM Flags: 1 total; -Xmx1G
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
Profiler Position: N/A (disabled)
Player Count: 1 / 8; [qj['HappySmurfday'/72, l='Happy Smurf Land', x=162.97, y=63.50, z=-120.85]]
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.

I too get this same issue. My server sill be running fine for a random amount of time 1 minute - 3 hours, and throw the same error. =/

Same happened to me and I use a veiew distance of 11

Same issue here, same error:

java.lang.IllegalArgumentException: Cannot get property bcl
{name=age, clazz=class java.lang.Integer, values=[0, 1, 2, 3, 4, 5, 6, 7]} as it does not exist!

But in my case only happens on my old world. If I create a new one on my server there is no problem so far.

So I should make a new world?

No just wait till Mojang releases a "b"

Ooops I made a new world.

Lol it doesnt matter I just thought you didnt want to start from scratch this issue will get fixed eventually

Well no crash so far with a new world.

Yep, happens for me, server jar on Ubuntu 13.10. Chunks stop loading, the error comes up in the server and players get kicked with the message io.netty.handler.timeout.ReadTimeoutException.

Making a new world fixed this issue for me. No more crashes.

My exiting server world I had since the snapshots for 1.7 started crashed in less a minute. I renamed the \world folder and started with a fresh map. ran fine for about 30 to 45 minutes (didn't time it), then it started crashing about every minute. I finally just restore my old map and went back to 27b for now.

Been running with my world for over an hour now. No crashes or anything.

Yes, you've made it clear that it doesn't affect new worlds; however, old worlds are still apparently very much affected by this bug.

Well changed block rendering.. so I assume that might be the issue.

It was the issue the last time they tried it. I worry we may have a terrain version schizm on our hands. (New system is incompatible with the old system.) Hope it can get ironed out.

My server crashed with a new world after about 30 to 45 minutes of having 5 players on it. After that crash, it was crashing about every minute.