FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
2 weeks ago
I have a webIq application where the used memory in ctrlX slowly grows until the core will go into error. Takes maybe 3 days or something until the error occurs. When looking in the core there are 26 processes active from webIq, and all are growing at the exact same rate. Maybe they are refering to the same memory area, I dont know. Until the error occurs, the webIq app and the core is working fine. Nothing strange at all.
Solved! Go to Solution.
a week ago - last edited a week ago
Hi @JohanRos ,
My first guess is that the application is generating a ton of logs and you've disabled the log file size limit. Can you check the size of the log file in the runtime manager?
Do you have any custom code used in the application that might be writing to the WebIQ server database?
There have been a few patches since your installed version as well. You can find the latest in the collaboration rooms.
a week ago
Tnx Sgilk for the reply! I will go to the customer today and check the log settings. I dont have any code for writing to the database, so I hope this will do the trick. I will uppgrade the app also. I will post the result of these changes.
Monday
This could also be due to using several recorders that record items with a lot of changes (WebIQ only records item changes in recorders)
Monday
I have a question here, the screenshot is for the used RAM memory, not disk memory (maybe thats not clear). How would writing to the SQLite database increase memory useage? Is the whole SQLite database kept in memory? (That's not how SQLite normaly operates)
Monday
Moved to corresponding sub forum Smart HMI - WebIQ Designer and Server.
Monday
Can you tell a bit about the HMI?
Are there any recorders? If you record data the items to be recorded have to be subscribed which each subscription of course using up a bit of RAM.
The more information you provide upfront on the HMI, usually the easier it is to get to a solution.
Tuesday
There are no recorders, and it seems that the new version of webIq app solved the problem. I upgraded the app the .10 and no the problem is gone. Thanks everyone for your help!
Tuesday