Also, mining blocks leave dark spots, and sunlight fails to update for some reason when I opened a cave up to a clear view of the sky. F3 works sometimes, but not always. Definitely affects all lighting, not just torches. Torches are just the most easily noticed.
Is it possible that this bug is only because its a snapshot? Maybe the code is running in a sub-optimized state and this will go away for pre-release. I can only hope I guess. I sure don't see it in 1.8. Its very bad. I am surprised others are not reporting it.
I added two more screen shots for this. A before with torch and then after the torch is removed. It is very easy to reproduce with the 16w snapshots. I wish this was voted on more.
Hmm this seems to happen more so when there's tick lag in the world or something like it. I switched from a command block heavy world to a fresh super flat world and the issue seems to not really be happening.
This happens because Minecraft will wait until no other chunk render updates are in some queue to schedule render updates for lighting, even if they are close to player. The one the block change occurs in is always updates because that's where the block got changed so it has to be updated.
This bug seriously messes with the look of a base I'm starting building. There's a glowstone below every glass block in the paths in this image. It's hard to visually tell if I've mob proofed an area properly. I've tried manually updating the bad chunks with the block/destroy forced update method, and sometimes it works for a little while, but eventually it reverts. This happens under optifine as well.
That’d be MC-80966 (empty cubic chunks don’t send over light information), this is about light not spreading correctly to chunk borders if just placed, and reloading chunks will fix this.
This issue may be relates to MC-3329