To decrease the physical memory usage of NX5, you can have the undo files written to disk instead when the physical memory is about to be exhausted by setting this environment variable :
Hi Hakan (Is this your firstname?) I experienced "Out of Memory" message many times during debugging either Open API code than Grip code. My opinion is that NX (I use NX4 still) doesn't release memory allocated during code execution at the end of execution. Have you any experience about this situation?
I apologize for my english and Thank you for your suggestion.
I Hakan, thanks a lot for your answer. I'll follow your suggestion then report to you the result. In the meanwhile,I've another problem. Can you hel me to define a component filter based on script using NX4?
3 comments:
Hi Hakan (Is this your firstname?)
I experienced "Out of Memory" message many times during debugging either Open API code than Grip code. My opinion is that NX (I use NX4 still) doesn't release memory allocated during code execution at the end of execution. Have you any experience about this situation?
I apologize for my english and Thank you for your suggestion.
I Hakan, thanks a lot for your answer. I'll follow your suggestion then report to you the result.
In the meanwhile,I've another problem. Can you hel me to define a component filter based on script using NX4?
will this work in NX4?
Post a Comment