At high frame rates, polling the system will block debugger messages.

[captain-dui]

GECS Version

6.7

What happened?

While maintaining a minimal number of entities and components, and minimizing additions and deletions to them, along with keeping the system lightweight to ensure the project runs at a high frame rate, excess performance will increase the frame rate.

However, unlike the trigger-based activation of entities and components, the system's debugger operates by polling every frame. This leads to the high frame rate multiplied by the number of systems exceeding Godot's default message limit, thus congesting the debugger.
This process will lead to a significant increase in memory usage.

Steps to Reproduce

Simply create a certain number of systems and ensure they run at a high frame rate.

[yuyonghuachang]

I'm having the exact same issue. I only have one system and two entities, but the moment I run it, the entire computer freezes up and then the program crashes abruptly.

[csprance]

Would be helpful to see what the code you're running looks like because I can run the debugger with about 1600 entities and see them all fine at 60fps

(I was able to push it to about 2800 before I started seeing Frame rate dips)

While there is always going to be some issues of speed when you have debugging enabled, this sounds like something else going on. Can you get me a repro?

[yuyonghuachang]

Please forgive the Chinese characters in my code. However, I believe this issue arises with simple systems and simple entities — when a game runs at a high frame rate like 240fps, the default message queue limit will be exceeded, causing a backlog in the debugger.

extends Entity
class_name E_储物格


@onready var 图像: TextureRect = %TextureRect


func on_ready():
	# Sync transform from scene to component
	var c_储物格 = get_component(C_储物格) as C_储物格
	if not c_储物格:
		return
	if c_储物格.物品内容 is 物品资源_类:
		%TextureRectself.texture= c_储物格.物品内容.显示内容

extends System
class_name S_储物格同步

@export var 资源:= preload("res://内部资源/物品资源/铜矿石.tres")

func query() -> QueryBuilder:
	return q.with_all([C_储物格])

func process(entities: Array[Entity], components: Array, delta: float):
# Process each entity - all systems use the same signature
	for entity in entities:
		var c_存储 = entity.get_component(C_储物格) as C_储物格
		c_存储.物品内容 = 资源
		entity.图像.texture = c_存储.物品内容.显示内容

I may not be able to reproduce this issue, as I found it suddenly disappeared in my project when I checked this morning. However, I think reproducing it would require a game that generates a certain number of messages per frame and running it at a high frame rate.