Confirmed memory leak issue in ETS (KNX) requiring attention
This post is to report a recurring and reproducible memory leak issue in ETS for KNX that requires attention.
During normal use, ETS shows a continuous increase in memory consumption over time. This is especially noticeable when:
-
working with larger projects
-
running ETS for extended periods without restarting
-
frequently downloading/programming devices
The increasing memory usage eventually leads to reduced performance, unstable behavior, and in some cases application crashes. Restarting ETS temporarily resolves the issue, but the problem consistently reoccurs, which strongly indicates a memory leak.
This behavior has been observed across multiple ETS versions and on different PCs, ruling out hardware- or operating-system-specific causes. All systems involved have sufficient available RAM.
Given the impact on stability and productivity, this should be treated as a software defect that needs investigation and resolution by the ETS development team / KNX Association.
-
For a long time I have noticed that ETS seems to run quite slow even on machines that should be easily able to handle it.
I have found that adding devices in to a project seems to have a particularly intensive use of resources causing fans to run full power on less powerful laptops.1 -
I’m experiencing the same situation here. I sometimes have ETS6 open for weeks, and I’ve noticed that it starts using many gigabytes of RAM. The server I use has 512 GB of RAM, but once the application reaches around 30 GB of usage, it becomes extremely slow and practically unworkable. The only solution is to restart it, which is also very slow and carries the risk of project corruption.
For a product of this scale that costs €1,000, this is quite unacceptable. We are clearly dealing with a software bug. I’ve done a lot of software development myself, and sometimes you need to set aside the team’s pride and hire external consultants to resolve persistent issues. That is something I would strongly advise the ETS development team to consider.
I’ve also noticed that there hasn’t been an update for almost nine months. In one of the recent posts, a team member mentioned the need “to test more before releasing,” which may imply that we will receive even fewer updates in the future.
Another thing I’ve noticed is that there is no general roadmap or milestone planning available from the ETS development team or the KNX Association. In the general readme, it literally states: “If we do provide a timeline, know that it is subject to change.”
I would suggest implementing at least a quarterly planning cycle, so issues are addressed at fixed intervals and there is consistent pressure to resolve long-standing problems.
As users, we deal with real-life situations. We cannot have our clients waiting months for solutions. If a KNX-based heating system is not functioning properly, we need to fix it within days. It is not fair to us as users that we have to wait so long for bug fixes.
This is a tool we use on a daily basis, and it needs to work reliably.
0
Opmerkingen
2 opmerkingen
U moet u aanmelden om een opmerking te plaatsen.