Evan A. Haskell
Comments
I noticed this is only an issue on superflat worlds of the Classic Flat and Bottomless Pit presets. I guess it has something to do with having a lot of open area near the bottom of the world.
Added 14w30c forced crash report
Or it could be changed to avoid randomly ticking certain blocks which it already does. See the bottom of g() at https://github.com/Bukkit/CraftBukkit/blob/master/src/main/java/net/minecraft/server/WorldServer.java (line 402 depending on when you're viewing it). Each block has an isTicking method which returns whether the block should be affected by random block ticking. Among other blocks, redstone torches return true. It just needs to be made to return false. But, as said by Panda, if random ticking is needed, then it should be made to check if the block is already queued.
I'm glad this was reported. I've often encountered torches behaving oddly and found that changing isTicking to false fixed the problems I was having.
Improved performance in 14w32a, but still an issue. It runs at 13-16 ticks per second now on certain superflats.