Difference between revisions of "Log Analysis"
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Log Analysis = | = Log Analysis = | ||
Logs can help you identify bugs and crashes, or other problems. Useful for troubleshooting and when modding. | |||
== Where to Find Your Logs == | == Where to Find Your Logs == | ||
Logs are stored in the install folder, under logs/ | |||
You can ignore the usageReport files, they're just summaries of the logs. | |||
== How to Read Your Logs == | == How to Read Your Logs == | ||
Wildermyth runs on java, and java stack traces are one of the main things you'll be looking for. Stack traces are easy to spot because they're a bunch of indented lines. The useful bit is generally the line above the stack trace, and sometimes the first few lines, for context. | |||
== Notable Entries == | == Notable Entries == | ||
| Line 27: | Line 29: | ||
Note: Here's an example of one that looks scary, but is pretty harmless! | Note: Here's an example of one that looks scary, but is pretty harmless! | ||
401:19:246 5 LegacyDesktop exiting due to fatal runtime error '''java.lang.OutOfMemoryError:''' Direct buffer memory | |||
at java.nio.Bits.reserveMemory(Bits.java:693) | |||
at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:123) | |||
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311) | |||
Note: We're aware there are some memory leaks and we'll be looking into it! | |||
[[Category:Modding]] | |||
[[Category:Documentation]] | |||
Latest revision as of 17:36, 3 January 2022
Log Analysis
Logs can help you identify bugs and crashes, or other problems. Useful for troubleshooting and when modding.
Where to Find Your Logs
Logs are stored in the install folder, under logs/
You can ignore the usageReport files, they're just summaries of the logs.
How to Read Your Logs
Wildermyth runs on java, and java stack traces are one of the main things you'll be looking for. Stack traces are easy to spot because they're a bunch of indented lines. The useful bit is generally the line above the stack trace, and sometimes the first few lines, for context.
Notable Entries
398:54:127 5 CampaignParticipantSystem AI player failed to join, aborting!
Note: This is a fatal error. We don't understand what causes it. It seems to be machine related and there are no known workarounds. We are still investigating it.
143:38:543 5 LegacyDesktop exiting due to fatal runtime error java.lang.IllegalStateException: frame buffer couldn't be constructed: incomplete attachment at com.worldwalkergames.legacy.render.NiceFrameBuffer.build(NiceFrameBuffer.java:93) at com.worldwalkergames.legacy.render.NiceFrameBuffer.<init>(NiceFrameBuffer.java:45) at com.worldwalkergames.legacy.game.mission.render.EnvironmentFrameSetup.validateSceneBuffer(EnvironmentFrameSetup.java:82) at com.worldwalkergames.legacy.game.mission.render.EnvironmentFrameSetup.render(EnvironmentFrameSetup.java:45) at com.worldwalkergames.legacy.render.LegacyRenderingSystem.render(LegacyRenderingSystem.java:82)
Note: This appears to be an out of memory bug.
398:44:768 3 CampaignGenerator exception during overland tile gen: java.lang.RuntimeException: unreachable tile!
Note: Here's an example of one that looks scary, but is pretty harmless!
401:19:246 5 LegacyDesktop exiting due to fatal runtime error java.lang.OutOfMemoryError: Direct buffer memory at java.nio.Bits.reserveMemory(Bits.java:693) at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:123) at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
Note: We're aware there are some memory leaks and we'll be looking into it!
