While working with the Integrity Client (Version 2009, SP7) I'm fairly often running out of memory with the error messages
"PermGen space" or
"Integrity Client out of memory" or
"MKS124804: Internal error detected: Error was: mks.frame.exception.OutOfMemoryApplicationError: Not enough memory: The application ran out of memory on the client or server."
on a Win7 64-bit machine with 4GB of RAM. As in those situations the Client often uses less than 500MB of memory and not much other tools running, there seems to be a client setting limiting the amount of memory.
I increased the maximum heap size to 1024MB, caching is set to 200MB.
Is it one of those settings or are there any others?
You may want to open a case with PTC Support for tuning this specific use case, but we had similar problems so the below may be helpful:
1) Sit with a user who can reproduce the crash and run "im mm --gui" in a command line to monitor the memory usage as the user goes through their activities. This exercise helped us isolate exactly what the users were doing to cause the memory usage spike, and work around it.
In our case, the culprit was editting a filtered IBPL with a huge set of values, however the memory only jumped up between the user clicking on the IBPL and saving the changes, so the recommended process became "select the IBPL value, click apply, then fill out the rest of the fields."
2) Take a look at the performance tuning guide here. There are tuning guides for each of the newer server versions, but the basic information does not seem to change much from release to release
3) Work with PTC Support to optimize the heap size and cache sizes in IntegrityClientSite.rc and other config files. Some of the values can only be configured in the text files and not through the client GUI. Also, modifying config files directly is always risky, so it is best to have guidance from PTC Support before attempting it.
This is most likely a specific setting in your Integrity configuration. If you open a case with support we can generally fix this problem very quickly, but we prefer to work directly with the client to ensure that there are no other factors causing this issue.
Please note that the likely changes needed to be made to correct this will require a server restart, so scheduling a restart (if nessesary) is a good idea before calling.
We are using Integrity 220.127.116.116 with service packs up to C160000000-037
Some of our users also have this MKS124804 error. Example:
Running a report that evaluates the links between Stakeholder Requests, Requirements, Test Cases and Test results is running out of memory
MKS124804: Internal error detected: Error was mks.frame.exception.OutOfMemoryApplicationError: Not enough memory: The application ran out of memory on the client or server
Please specify exactly which configuration files on the client should I verify ?
What parameters ?
You probably wanted to start your own discussion thread here, as this thread was around 7 years old.
Here is a general troubleshooting article related to the general out of memory issue with Integrity:
But you'll probably want to open a Support case with the Integrity Support folks, as they can look at why you're running out of memory. If you do open a Support case with them, try to provide them with an Integrity Server/client support package, as that is most helpful for them.