Just want to share my recent experience. In LV preferences one can
check a checkbox allowing to de-allocate memory as fast as possible. I had
it checked because some time ago I had to deal with large arrays and LV did
not seem to return the memory to the system after computations where over.
So it was sitting there in background on > 100M of RAM (or swap) even after
a 10 minutes or so.
Today I decided to play around with some ActiveX stuff. Downloaded
toolbar.llb from NI website, and that example would run once properly, but
next attempt would invariably result in crash. Error message was along the
lines of either a memory access error or illegal instruction, one time the
instruction was trying to reach a memory with the
same address as itself. I
also built my own little toolbar to see if problem was with an example using
older version of controls, that was not a case.
Then I tried the same thing on other machine, and there it worked like a
charm. Other machine is my troubleshooter where I never install any junk,
and in general keep untouched. Basically the problem was that little
checkbox. Seems that memory manager has become more efficient in LV 5.1
because I have been having these memory access errors quite often since LV
5.1 upgrade.
This error is basically a bug, VI and memory manager should check out
what has happened with the system since the last run. I was all set to make
a nice toolbar, but annoying little bug, ruined my evening.
Hope it helps somebody. Anyone else have these memory errors? (It happens
in win98 and NT as well, so it is not an OS issue, well as far as MS OS
goes)
