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.

[captain-dui]

ecs.zip

i've unploaded my test project.the key points are that i change the godot editor settings,enabled the gecs debugger,and set the fps to unlimited.
@csprance

[csprance]

From what I understand the issue is more to do with the fps being unlimited. Why do you need to do that. You're then causing the game to poll 1000+ times in a single frame. I'll accept a PR for this that limits the debugger polling but I'm not planning on solving an issue that only happens when you change settings and do things that are not recommended. From what I can tell setting max fps is not recommended unless you have a good reason.

…

On Thu, Feb 12, 2026, 11:16 PM captain-dui ***@***.***> wrote: *captain-dui* left a comment (csprance/gecs#77) <#77 (comment)> ecs.zip <https://github.com/user-attachments/files/25279792/ecs.zip> i've unploaded my test project.the key points are that i change the godot editor settings,enabled the gecs debugger,and set the fps to unlimited. @csprance <https://github.com/csprance> — Reply to this email directly, view it on GitHub <#77 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB4JLGIX6SJSACPRLIQXCV34LVFZVAVCNFSM6AAAAACPKZNDI2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQOJUG43DANZTGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[captain-dui]

I agree this might be not a typical case because i changed the default setitings,
then i changed the max fps to 120,the debugger still gets clogged,
which leads to memory growth and eventually freezees the engine.
In other words,running 19 systems at 120fps will cause it freez,
and if you lower the fps to 60 while doubling the number of systems to 38,you will get the same result.
Due to the accumulation of messages in the godot debugger,memory usage appears to increase without bound.
So even at 60 fps,the numbre of systems that can run still seems to be somewhat limited.

Finall, i would argue that this is actually a common scenario. godot's default fps cap is unlimited.it just has vsync enabled by default,which effectiively limits the fps to 60.i think disable vsync may not uncommon.

据我所知,这个问题更多与fps的存在有关
无限。
你为什么需要那样做。然后你让游戏进行1000+的投票
单帧时间。

我会接受一个限制调试器投票的PR,但我不
计划解决一个只有在更改设置时才会发生的问题
做一些不推荐的事情。根据我能说的设置最大fps是
不建议,除非你有充分的理由。
......