Memory never freed - RAM keeps increasing

Submitted by alex_38 on Thu, 07/17/2014 - 08:13
Forums: 
Journaling / NXOpen API

Hi,

I have a problem with my openNX dll. My dll is sketching many things.
But when it ends, it doesn't free the RAM it has allocated ... On a same NX sesssion, if I ran my dll several times, the RAM will continue to increase. I check that after every commit, I destroy the features, but the problem is still there.

I have to exit NX so the RAM is freed.

I don't allocate anything. I just have a lot of features (like 3000).

Is there someone who had the same problem ?

Thanks a lot

NXJournaling - Fri, 07/18/2014 - 06:04

How much is your RAM usage increasing? Are we talking Megabytes or Gigabytes? Is it crashing your computer?

If your journal is creating a lot of features (3000 qualifies as a "lot of features"), I'd expect RAM usage to increase after the journal is run as the new features will now have to be stored in memory.

If your journal is only creating a few new features, I would not expect a significant increase in RAM usage during or after journal execution.

alex_38 - Tue, 07/22/2014 - 02:35

I have a lot of features, so I understand why the RAM increases. ( like GigaBytes).

What I don't understand is, why, when I close the part, the RAM is not freed.
As I'm testing several time my dll on an empty part, the RAM keeps increasing. I can only free the RAM by closing NX.

Is it normal ? Is it more a NX problem ?

Thanks

NXJournaling - Tue, 07/22/2014 - 06:29

As new features are created, I'd expect memory usage to increase. However, GB's of usage sounds excessive. Unfortunately, I have no special insights on the internal workings of NX. I'd suggest contacting GTAC with your code (or preferably a short sample that shows the same behavior) to have them look into it.