Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using F5 (show BT editor) in-game during multiplayer causes crash via NPE

See original GitHub issue

What you were trying to do

Open the behavior tree editor in-game via F5

What actually happened

Client crashed with an NPE

How to reproduce

Client connected to a multiplayer server with Behaviors active (assumed, might take less)
Press F5

Log details and game version

Omega 900 during today’s play test

14:03:27.201 [main] ERROR o.terasology.engine.TerasologyEngine - Uncaught exception, attempting clean game shutdown
java.lang.NullPointerException: null
	at org.terasology.rendering.nui.TextLineBuilder.addText(TextLineBuilder.java:56)
	at org.terasology.rendering.nui.TextLineBuilder.getLines(TextLineBuilder.java:51)
	at org.terasology.rendering.nui.TextLineBuilder.getLines(TextLineBuilder.java:46)
	at org.terasology.rendering.nui.itemRendering.StringTextRenderer.getPreferredSize(StringTextRenderer.java:69)
	at org.terasology.rendering.nui.widgets.UIList.getPreferredContentSize(UIList.java:117)
	at org.terasology.rendering.nui.internal.CanvasImpl.calculateRestrictedSize(CanvasImpl.java:347)
	at org.terasology.rendering.nui.internal.CanvasImpl.calculatePreferredSize(CanvasImpl.java:333)
	at org.terasology.rendering.nui.layouts.ScrollableArea.getPreferredContentSize(ScrollableArea.java:193)
	at org.terasology.rendering.nui.internal.CanvasImpl.calculateRestrictedSize(CanvasImpl.java:347)
	at org.terasology.rendering.nui.internal.CanvasImpl.calculatePreferredSize(CanvasImpl.java:333)
	at org.terasology.rendering.nui.layouts.miglayout.MigComponent.calculatePreferredSize(MigComponent.java:41)
	at org.terasology.rendering.nui.layouts.miglayout.MigLayout.layoutContainer(MigLayout.java:223)
	at org.terasology.rendering.nui.layouts.miglayout.MigLayout.getPreferredContentSize(MigLayout.java:182)
	at org.terasology.rendering.nui.layouts.miglayout.MigLayout.getMaxContentSize(MigLayout.java:188)
	at org.terasology.rendering.nui.internal.CanvasImpl.calculateMaximumSize(CanvasImpl.java:362)
	at org.terasology.rendering.nui.internal.CanvasImpl.drawWidget(CanvasImpl.java:385)
	at org.terasology.rendering.nui.CoreScreenLayer.onDraw(CoreScreenLayer.java:115)
	at org.terasology.rendering.nui.internal.CanvasImpl.drawStyledWidget(CanvasImpl.java:406)
	at org.terasology.rendering.nui.internal.CanvasImpl.drawWidget(CanvasImpl.java:392)
	at org.terasology.rendering.nui.internal.NUIManagerInternal.render(NUIManagerInternal.java:475)
	at org.terasology.engine.modes.StateIngame.renderUserInterface(StateIngame.java:235)
	at org.terasology.engine.modes.StateIngame.render(StateIngame.java:219)
	at org.terasology.engine.subsystem.lwjgl.LwjglGraphics.postUpdate(LwjglGraphics.java:166)
	at org.terasology.engine.TerasologyEngine.tick(TerasologyEngine.java:446)
	at org.terasology.engine.TerasologyEngine.mainLoop(TerasologyEngine.java:400)
	at org.terasology.engine.TerasologyEngine.run(TerasologyEngine.java:376)
	at org.terasology.engine.Terasology.main(Terasology.java:154)
14:03:27.201 [main] INFO  o.terasology.engine.TerasologyEngine - Shutting down Terasology...

Maybe of interest to @l0ftyWhizZ and/or @Naman-sopho since they’re digging around in the BT area. Probably an easy fix?

Issue Analytics

State:
Created 5 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

Cervatorcommented, Jun 17, 2018

Closing this as complete. The button was just removed technically after v2.0.0 but still the crash etc was fixed then so leaving this issue in that milestone still.

0reactions

Cervatorcommented, Apr 9, 2018

Yeah I suppose the button made sense back when BTs were purely in the engine. Now they require at least the Behaviors module active. So lets add to this issue outright removing that button from the main menu. At least until we have the ability to activate modules inside the main menu.

Top Results From Across the Web

Windows stop error/hard crash error has noticed while ... - AskF5

Windows users experience a blue screen of dead (BSOD) or windows stop error/hard crash error while they connect to edge client.

iRules with persist command might causes tmm crash ... - AskF5

When a virtual server is configured with HTTP or HTTP/2 profile along with irule containing 'persist add' command, HA pair experiences a ...

Supplemental Document: BIG-IP 15.1.5 Fixes and Known Issues

Cumulative fixes from BIG-IP v15.1.4.1 that are included in this release ... ordered items via tmsh might cause errors when adding new items...

Problems that cause crashes, panics, hangs in BIG-IP ... - AskF5

F5 Networks Product Development tracked these issues under the specified CR numbers. These issues affect only the listed version ranges and were ...

BIG-IP 16.1.2.1 Fixes and Known Issues - AskF5 - F5 Networks

TMM crashes on SIGSEGV. Conditions: This can occur while passing traffic through the message routing framework. Impact: Traffic disrupted while tmm restarts.