ETS - Error (The system does not have enough memory to process this command...)
ΑπαντημένηDear Team Support,
I have running with this error on ETS several times when working on ETS.
ETS - Error
The system does not have enough memory to process this command. Please try to split the operation into smaller steps. The ETS will close now.
After this error the ETS closes and I have to open it again (sometimes I lost progress changes on the project).
This errors occurs when I restore more than 3 projects from backup archive, but some times I can restore more than 3, sometimes less.
When I have more than 1 ETS project open and switch from tabs or open local projects, etc, sometimes this error also occurs.
I have more people in our team that this errors occurs.
Can you somehow check if this is a problem with the software, because the ETS closing without a reason it's having a lot of impact on our workflow.
Thank You
Kévin Simões
-
Επίσημο σχόλιο
Hello Kévin, I have created a support ticket out of this request so that we can handle it with our developers. Let's continue the discussion there.
Regards, Vassilios
-
I get also this error sometimes. But with this error the ETS does not crash.
0 -
Is there an update on the cause of this issue. I'm running into the same thing and cannot start ETS anymore.
However with me it occurs when just starting ETS6 immediately after opening the app with the shortcut
0 -
KNX support suggested that to overcome the problem in question, I should disable Compatibility Mode.
However, I still have the problem of ETS6 closing due to lack of memory.
One time it happened to me with ETS6 open and I hadn't performed any operations on ETS6.
At this moment I cannot operate the ETS6 as normally as I did before.
0 -
This is still a big problem. My ETS crashes more than 3 times a day because of the problem Kevin wrote. Is there an update soon to solve this problem?
2 -
I also have the same experience on my laptop. Have not found a solution yet
2 -
Hi, same problem for me and my colleagues. ETS 6, mstly on Win 11. We use the archive in collaboration mode and it happen reularly when we archive project.
1 -
Same problem really anoyng yer ago posted and no sollution......?
1 -
https://support.knx.org/hc/en-us/articles/360000261424-Product-Store-data-is-corrupt
This solved my problem. I had the error message pop up after starting the ETS 5.7.7. First the pop-up loading window showed and the text at the bottom was something like: updating prduct catalog cache. Then the memory usage of the ETS went up slowly to around 3GB, and then I got the same memory error message. This is what solved it for me.
0 -
same problem for me on ets 6.3 (newest update).
It is almost impossible to work. ETS freezes for 30 sec- 1 minute and then sometimes come back to normal and sometimes I get the Not enough memory error.
I am lucky if I can work 5 minutes without crash.
log entries :
2025-05-18 21:08:15,042 [23] INFO Knx.Ets.ProjectArchive.Services.ArchiveWatcher - Changes detected: Additional: Files: 1, Directories: 0 Removals: Files: 1, Directories: 0
2025-05-18 21:08:15,797 [20] INFO Knx.Ets.ProjectArchive.Services.ArchiveWatcher - Changes detected: Additional: Files: 1, Directories: 0 Removals: Files: 1, Directories: 0
2025-05-18 21:08:16,438 [36] INFO Knx.Ets.ProjectArchive.Services.ArchiveWatcher - Changes detected: Additional: Files: 1, Directories: 0 Removals: Files: 1, Directories: 0
2025-05-18 21:08:17,295 [1] ERROR ETS.EtsBootstrapper - System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at MS.Internal.WeakEventTable.Purge(Boolean purgeAll)
at MS.Internal.WeakEventTable.CleanupOperation(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
2025-05-18 21:08:18,510 [4] INFO Knx.Ets.ProjectArchive.Services.ArchiveWatcher - Changes detected: Additional: Files: 1, Directories: 0 Removals: Files: 1, Directories: 0almost unusable now.
reinstalled, cleaned all files form Program Data but happens all the time!
FIX PLEASE!!!
0 -
Does this sound familiar? When your KNX project grows (more devices, more group addresses, more parameters), ETS ends up hogging all the memory and turns into a bit of a tortoise. Why does this happen? Well, check it out:
-
Memory “cap”
ETS is a 32-bit application, so it can’t use more than about 2 GB of RAM. As soon as your project pushes it, bang—it hits the ceiling and everything slows to a crawl or throws “out of memory” errors. -
Saving everything at once
Every time you add or change something, ETS rewrites large chunks of the project file. It’s like reprinting an entire book just to tweak one paragraph: slow and with a lot of disk thrashing. -
Logs and backups that bloat
Notes and backups keep growing unchecked—ETS doesn’t purge them automatically, so your project file balloons and the tool has to load more and more each time it starts. -
Single-lane processing
It doesn’t take advantage of multiple CPU threads, so if anything takes a while (importing data, writing a backup, reading a huge catalog), the entire interface freezes until it’s done.
IT’S A SHAME THAT ALL OF THIS IS THE WAY IT IS, BUT IT’S WHAT WE’VE GOT UNTIL SOMEONE POUNDS THE TABLE.
0 -
-
It is impossible to work!
I have just updated to ETS 6.3.1
I opened my project and left the pc untouched.
3 minutes later:
It is a serious issue that makes my work undoable!
How is this is possible with a 1000 € application?!
0 -
Everytime time i leave the pc untouched for a few minutes, this error occurs.
I have also had problems when i adressing DALI and the same error occurs, then i have to redo everything because it is not saved automatically in all DGs.
Leonardo Garcia Rufino seems to have a good ode of where the problem lies, so why isn´t anything being done?
0
Σχόλια
13 σχόλια
Πραγματοποιήστε είσοδο για να αφήσετε ένα σχόλιο.