[Bug] RegisterConsoleListener Fatal Error

[1A3Dev]

Summary

Using RegisterConsoleListener in a server-side lua script results in fatal assertion failure each time the console tries to show a new log line

Issue type

Server

Repro rate

Always

Server build version

FXServer-early-access b90 win32

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

Windows

OS version / distribution

Windows 11 25H2

CPU

AMD Ryzen 5 5600X

RAM

32 GB DDR4

Using txAdmin?

No

Hosting provider

Self-hosted

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Put the following code in a server-side lua file: RegisterConsoleListener(function() end)

Expected Behavior

It should register the console listener like normal and shouldn't error when a log happens.

Actual Behavior

It errors each time the console tries to log with an an assertion failure.

Evidence

Additional Context

No response

[william-des]

Same thing happen in JS, but seems to happen only when doing I/O. Here is a repro code

// Minimal reproduction: a resource that has registered a console listener via
// RegisterConsoleListener hard-crashes the server the moment it performs any
// outbound TCP socket I/O.

const net = require("net");

RegisterConsoleListener((channel, message) => {
	// Intentionally a no-op: the crash does not depend on the callback body.
});

const server = net.createServer(socket => {
	socket.write(Buffer.from([0x0a, 0x0b, 0x0c, 0x0d]));
});

server.listen(0, "127.0.0.1", () => {
	const port = server.address().port;
	console.log("[repro] node:", process.version);
	console.log(`[repro] local server on 127.0.0.1:${port} — connecting (this triggers a Net permission check line) ...`);

	const client = net.connect({ host: "127.0.0.1", port }, () => {
		console.log("[repro] connected, waiting for inbound bytes...");
	});
	client.on("data", buf => {
		console.log("[repro] received", buf.length, "bytes — NO CRASH (listener must be disabled)");
		client.destroy();
		server.close();
	});
	client.on("error", e => console.log("[repro] error:", e && e.message ? e.message : e));
});

[titanium-cfx]

A fix for this bug has been implemented and will be available in an upcoming hotfix patch that will go live within the next two hours. Please try again once the patch is live and let us know if the issue persists. Thanks for your help!

[1A3Dev]

seems to be resolved 👍🏻