zach

Affects 1.20.4

I did search but only searched for torch related bugs sorry.

😞

doubt it is specs, I've gotten it both on a GTX970 desktop rig and an integrated card. The lighting bugs also sync between all clients on a server and mobs spawn in the incorrectly lit areas.

Bug still present in 1.14.1. A different set of chunks breaks on each server reboot, isn't just client side as the lighting stays identical after relog and mobs do spawn in the "unlit" areas. The only way to correct this that I have found is to break every source of light and replace, as even causing a block update does not fix it.

Also reloading my world in a 1.14.1 server caused new light issues, it did not just retain the old ones.

Confirmed on 1.14

he said past 1.6 that means it includes the current update I'm having the same problem and when it crashes it doesn't create a crsh report and the output log does not show it crashing and its on a vanilla launcher and game if i shut down my internet while hitting play then turn it on when it opens i can play

here is my output log:

3989 debugs7 infos
17:19:48 launcher Preparing to launch minecraft client for 1.12.1
17:19:48 launcher Checking installations.
17:19:48 launcher Minecraft client 1.12.1 is ready to start.
17:19:48 launcher Starting!
17:19:49 launcher Using default game log configuration client-1.12.xml (outputs XML)
17:19:53 bib Setting user: snowydragon
17:19:56 bib LWJGL Version: 2.9.4

i have the same issue and when i look for the crash reports there are none

dowlaoded launcher starts and then bamm back to laucher bug page this is what i get....... i dont know anything about pc i just want to play.

[09:16:12] [Client thread/INFO]: Setting user: FatalTrees
[09:16:12] [Client thread/INFO]: (Session ID is token:1dcaa55b40de4141ad716ea7c74c36ac:3619a68da8c840e7bf629bdf0b504579)
[09:16:15] [Client thread/INFO]: LWJGL Version: 2.9.4
[09:16:16] [Client thread/INFO]: Reloading ResourceManager: Default
[09:16:19] [Sound Library Loader/INFO]: Starting up SoundSystem...
[09:16:19] [Thread-6/INFO]: Initializing LWJGL OpenAL
[09:16:19] [Thread-6/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[09:16:19] [Thread-6/INFO]: OpenAL initialized.
[09:16:20] [Sound Library Loader/INFO]: Sound engine started
[09:16:22] [Client thread/INFO]: Created: 512x512 textures-atlas
#

1. A fatal error has been detected by the Java Runtime Environment:
   #

2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x48813e88, pid=5488, tid=5304
   #

3. JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)

4. Java VM: Java HotSpot(TM) Client VM (25.25-b02 mixed mode windows-x86 )

5. Problematic frame:

6. C [ig4dev32.dll+0x3e88]
   #

7. Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
   #

8. An error report file with more information is saved as:

9. C:\Users\Ralph\AppData\Roaming\.minecraft\hs_err_pid5488.log
   #

10. If you would like to submit a bug report, please visit:

11. http://bugreport.sun.com/bugreport/crash.jsp

12. The crash happened outside the Java Virtual Machine in native code.

13. See problematic frame for where to report the bug.
    #
    AL lib: (EE) alc_cleanup: 1 device not closed
    Java HotSpot(TM) Client VM warning: Using incremental CMS is deprecated and will likely be removed in a future release

This and the invisible chest bug need to be fixed.

This is most noticeable on short (and maybe tiny) render distance.

As of now I have had 2 worlds ruined by this bug.
PLEASE fix this in 0.9.0!

1. yay some on uses ubuntu!
2. werd

Please fix this. I need them for my house.
(And I don't want to cheat)

Mojang, can you PLEASE fix this in 7.0?

hopefully a solution will be found soon.

oh thank you for telling me!

I think this is the auto-jump.

That's what happened to my world...

This happens with all slabs

I saw this in the live stream video. Why didn't they notice?