Simexe remain in memory after changin the model

[BT_canadair]

In Version 7.1.5 and 7.1.6 I am noticing that simexe.exe remains in memory even when I change my model.
In many cases this simply causes the memory usage to increase (sometimes significantly during many small simulations) however, more and more this is causing ERROR in either the trim, lin or analyze commands.

Why is simexe.exe not removed from memory when I change my model?
How can I avoid these errors (without running "undefine simexe" repeatedly)?

[Richard P.]

Hi BT,

Are you using File>>Exit to exit the current model? That is the cleanest exit to stop simexe from running. Also, you can use Ctrl-BReak or Ctrl-C to exit abruptly.

[BT_canadair]

Richard,

The scripts that I'm using change my base model using SBA (add/remove dynamics and perform some simplification).

After "changing" the model I them run analyze/trim/lin/step/freq etc... this is where I have problems.

The same tools running the same model did not experience these error on Version 7.1.4.

I get memory allocation errors, application error - memory could not be read, and other frequently.

Thanks,

Brian

[Richard P.]

Hi Brian,

Can you attach a script which demonstrates this behavior? We think it is a bug and would like to verify. To clarify, it only comes up after running a sufficient number of scripting commands or is there one script in particular which causes the problem?

Thanks for your help in identifying this,
Richard

[Richard P.]

Hi Again Brian

This problem you are noticing is probably related to a fix which went into version 7.1.6. The developers are very interested in your case and working a fix very soon into a new release of 7.1.6.

If you can get in touch with me here soon, I would like to discuss taking this issue offline to email or phone conversation.
If you like, just let me know on this forum if that would be OK.

Thanks,
Richard

[BT_canadair]

Good Morning Richard,

I was going to get back to you yesterday, but wanted to create a simple test case for you (this is In Progress).

The error is comming up while running some of our design scripts which perform many simple tasks:

[BT_canadair]

Good Morning Richard,

I was going to get back to you yesterday, but wanted to create a simple test case for you (this is In Progress).

The error is comming up while running some of our design scripts which perform many simple tasks:

     such as: Using SBA to add/remove some dynamic elements, using filters with "parameteric" (%variable) coefficients which can be updated by the scripts.

We are running the "same" model structure, but modifying the contents. We then typically run simulations, linearizations + step/freq to analyze the new system.

If I bring up the task manager and sort by Memory Usage, thge simexe.exe that is opened when the script is called just keeps growing. Even once the script is completed, the task remains. If I launch the scripts again the memory usage continues to increase.... eventually consuming a large amount of memory/virtual. On my 2x3.2Ghz with 2G RAM I have seen it take up to 1.9G of total RAM before I start getting errors. These include Windows pop-up related to memory could not be read, xmath debugger with errors on lin() system is null.

I will email a small model and basic script to you.

Thanks

Brian

Message Edited by BT_canadair on 01-06-2006 08:14 AM

Message Edited by BT_canadair on 01-06-2006 08:15 AM

[Richard P.]

Hi Brian,

Thanks, as I mentioned the developer is curious to see if it is the same area which was altered slightly in the recent past.
I can't post my email address here, if you have code that is not under any security concerns you can attach it to the forum post. If you do not want to post your example publicly we can think of something else.

[BT_canadair]

Richard,

I have sent simple model and a small command to Ian F. to pass on to you.

Thanks,

Brian

[Richard P.]

Hi Brian,

Thanks for sending the model and a good demo script. I have run it and observed the increasing memory usage of simexe. I am going to relay that to the developer so he can find out if it is the same issue.