MCL-12594Game output log fails to show exception stack traces
The bug
The game output log sometimes just does not display exception stack traces.
Clicking repeatedly on arbitrary filter buttons (e.g. "fatal" even if there are no fatal log messages) might show the exception stack traces.
How to reproduce
- In Minecraft use the following command
/summon armor_stand ~ ~ ~ {CustomName:invalid-json}
It should fail because the CustomName is not valid JSON - Look in the launcher log
It only shows the warning text "Exception loading entity:", but the stack trace is missing. You can verify that the game logged the stack trace by looking at the log file.
Linked Issues
Created Issue:
Game output log fails showing exception stack traces
The bug
The launcher log sometimes just does not display exception stack traces.
Clicking repeatedly on arbitrary filter buttons (e.g. "fatal" even if there are no fatal log messages) might show the exception stack traces.How to reproduce
- In Minecraft use the following command
/summon armor_stand ~ ~ ~ {CustomName:invalid-json}
- Look in the launcher log
Linked Issues
The bug
The
launcherlog sometimes just does not display exception stack traces.
Clicking repeatedly on arbitrary filter buttons (e.g. "fatal" even if there are no fatal log messages) might show the exception stack traces.How to reproduce
- In Minecraft use the following command
/summon armor_stand ~ ~ ~ {CustomName:invalid-json}
- Look in the launcher log
The bug
The game output log sometimes just does not display exception stack traces.
Clicking repeatedly on arbitrary filter buttons (e.g. "fatal" even if there are no fatal log messages) might show the exception stack traces.How to reproduce
- In Minecraft use the following command
/summon armor_stand ~ ~ ~ {CustomName:invalid-json}
- Look in the launcher log
relates to
is duplicated by
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
Game output log fails showingexception stack tracesGame output log fails to show exception stack traces
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
The bug
The game output log cuts off messages if they are too long, but does not show a scroll bar either. Resizing the windows might not help because it first tries to fit additional columns, such as class and thread name.
Note: The behavior changed slightly, possibly due to the fix for MCL-12594. This now only occurs if the message does not contain whitespaces.
How to reproduce
- In game, run the following command
/say aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaEND
- Check in the game output log whether you see "END"
It is cut off and there is no way to scroll
Resolved it as duplicate of MCL-12594 because that report is more generic.
Duplicates MCL-12560
You are right,
MCL-12560describes the same issue. However, I will close that report as duplicate since this one is more generic. Would you like to become the reporter of this report and keep it up to date?Confirmed with stack trace for resource pack errors and shader compile errors.
Fixed. Tested in 2.1.10837 (Beta)