Skip to main content
1-Visitor
February 10, 2013
Solved

funny memory problems Mathcad 15

  • February 10, 2013
  • 2 replies
  • 3131 views

After removing some variables in the programm, Mathcad still behaves like a donkey not willing to surpass 5000 iterations creating new vectors <1000 entries long. The latest error message is about "accessing protected memory" indicating "corrupt memory". Does this refer to physical memory?

My configuration is 3 GB used memory with 32 bit W7.

Is there an easy way to get back som flexibility, using larger matrizes?

thanks

Best answer by StuartBruff

Efried wrote:

Hello Stuart many thanks for the endeavour. Got the attachemnt lost?

at each simulation vectors are handed over to a subprogramm and new ones created by the sub programm and handed over via the programm

regards

Umm, no, it didn't get lost. I got distracted halfway through by my wife asking me to yell at my 10 year-old who, in turn, got distracted by TV (or turned temporarily deaf by it) when asked to tidy up the bathroom after him! Posted without checking, I'm afraid. Mea Culpa.

Stuart

PS. What Werner says.

2 replies

23-Emerald V
February 10, 2013

Could you clarify what you mean by "5000 iterations creating new vectors < 1000 entries long"? Do you mean like the attached which runs a loop n times that creates a new vector of length m (erasing the old one) or creates n distinct new vectors or ...?

If you run the attached worksheet, do you get memory errors? I don't runnning it on a 32-bit Win 7 Ultimate with 4GiB RAM.

Stuart

Efried1-VisitorAuthor
1-Visitor
February 10, 2013

Hello Stuart many thanks for the endeavour. Got the attachemnt lost?

at each simulation vectors are handed over to a subprogramm and new ones created by the sub programm and handed over via the programm

regards

25-Diamond I
February 10, 2013

Probably posting a stripped down worksheet which reproducably throws the error on you machine would be of more help than a vague description!?

Efried1-VisitorAuthor
1-Visitor
March 13, 2013

after debugging quite some mathcad code I'm sure that the stack function creates the memory problems. It is not only slow.