NX9 - RAM Memory problem

[SvenVoeten]

Hi Everyone,

When I'm programming in NX after a while my pc is slowing down because NX is taking up all my RAM memory.
I'm not using large assembly's or extreme complex workpieces.
It seems that it doesn't matter what I open or how many files but how long NX is running.

My pc specs:
Intel Core I7-3610QM boost to 3.3Ghz
Nvidia GeForce GT 650M
8GB DDR3 RAM
750GB HDD

Greetings Sven

 

[grinch33]

Whats your program doing? What language?
Sounds like you have a memory leak!

Graham Inchley, Systems Developer, Sandvik Coromant.

http://www.sandvik.com

HP EliteBook 8760w, Win7, 16GB. Developing in: Java | C | C# | KF
Production: NX6.0.5.3 MP5
Testing: NX8.5.3.3 MP4 64bit | NX9.0.2.5

 

[Tingsryd]

Hello Sven,
You did not mention what version of NX you were running. I remember older NX versions had more memory leakage and other issues such as internal memory errors. I recall working on large, 3D parts when things would slow down as the day went on with more and more ram being used. Also I would encounter some errors that would seem illogical to occur so I would exit the part and restart NX and same operations would generate without errors so I knew NX was having some issues. I hardly experience those error messages any more and I do not notice any significant memory leakage.

My typical ram usage is around 6-9 GB but when I use parallel generate on large parts, and also reference tool, I use a lot more ram; probably 10-16 GB. Once in a while bad models will cause problems but that is no fault of NX.

NX9
Waiting for 10.2

 

[SvenVoeten]

What do you mean by what is my program doing?
I'm not writing any code or so. I'm programming in NX CAM.

 

[grinch33]

Oops, sorry.
In my world 'programming in NX' means writing automation code using NXOpen. In that case it can be very easy to exhaust all of the RAM if you are careless.


Graham Inchley, Systems Developer, Sandvik Coromant.

http://www.sandvik.com

HP EliteBook 8760w, Win7, 16GB. Developing in: Java | C | C# | KF
Production: NX6.0.5.3 MP5
Testing: NX8.5.3.3 MP4 64bit | NX9.0.2.5

 

[Tingsryd]

Sven,
What version of NX are you using?
What operations are you using?
Are you using IPW?
Are you using reference tools?

NX9
Waiting for 10.2

 

[SvenVoeten]

I'm running NX9.0.3 64-Bit version
Sometimes I get "memory access violation" but that happened not very much since i use NX9.
In NX8 I would get that regularly. (That was also on another PC)

 

[SvenVoeten]

I'm using planar milling, contour milling and multi-axes milling operations.
When I'm using only planar and contour milling operations I have the same problem.
Not using any reference tools. I do use IPW.

 

[Tingsryd]

What about your operations? What types are you using?

NX9
Waiting for 10.2

 

[Tingsryd]

Sorry my replies are out of order. Eng Tips cannot keep up the pace!

Can you attach a prt file for us to look at?

NX9
Waiting for 10.2

 

[SvenVoeten]

The file that I've included is not the most complex one were I've worked on.
But I had the problem with this file.

When I open this part, I've plenty of RAM-memory,
but when I'm working on it for a while my memory usage increases.

 

[SvenVoeten]

This is another component to the one before.

 

[SvenVoeten]

This is the last component and the main set-up file.

I'm also using tools from the library that I've created.

 

[JohnRBaker]

After opening all of your parts in a clean session of NX 9.0, my system allocated a maximum of 338 MB of memory.

Opening the largest assembly that I have on my laptop, something close to 12,000 components, only required 1257 MB, but that was using 'lightweight' representations. Loading the same Assembly, only this time using 'exact' representations, required 1388 MB.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[Tingsryd]

Simply opening parts will not demonstrate a lot of ram usage; we need to generate operations that are ram intensive.

Sven,
I opened the parts but there are not any manufacturing operations. If there isn't a confidentiality issue it would be a good idea to attach a file with operations you are having problems with. The parts I see a lot of ram usage are large 3D parts that have reference tool operations and/or using IPW with small tools. Especially using IPW after some finishing as been done on a large 3D part.

Can you attach a file with operations you are having problems with?

NX9
Waiting for 10.2

 

[SvenVoeten]

That's strange, when I open the setup file there are operations.

I've attached it again but in a zip file. There is a map in the zip file where the right components are located.
Can you try again and open the setup file again, normal there should be operations.

This is a workpiece that I've made a few days ago. When I was working on the program I've had to restart NX each 15 minutes because my RAM memory was full.

 

[Tingsryd]

I opened your setup part and all the operations generated almost immediately. The only message I received was pertaining to the ipw being out of date when I generated the operations on the other side of the part but they still generated quite fast. I was hoping to see the same behavior as your computer but it is okay on my computer. I would call GTAC and maybe there is something in your log file they can use.

I am running 9.0.3.4 mp4.



NX9
Waiting for 10.2

 

[SvenVoeten]

If I open the file now and I generate everything there is no problem, the problem is when I'm working for a wile on the file.
It seems like it remembers everything and stores it in my RAM memory so eventually it would be full.

I'll contact them, thanks for the help.

 

[Tingsryd]

One last thing, I wonder if your dialog memory file is becoming too large. NX manufacturing has a bad habit of making the dialog memory file too large to be useful. If that file gets too large I know start-ups and shutdowns can take a long time. If you have never cleared it then I recommend doing so. The easy way to do that is in User Interface preferences and press the Reset Dialog Memory button. Be warned this will cause NX dialogs to revert to default but only the first time you use a dialog.

NX9
Waiting for 10.2

 

[SvenVoeten]

I've deleted that file already, I read it on another topic that that could be the problem but no help for me.