11-20-2007 02:49 PM

11-20-2007 05:01 PM
11-20-2007 08:37 PM - edited 11-20-2007 08:39 PM
The code had a sub vi which provided data to a single multi-line graph using a 2D array. The subvi was within a loop with shift registers so that if the operator repeated a measurement, it would redraw only that measurement (other line untouched). The graphs were replaced by individual ones. No problem there.
The sub-vi was modified to simply obtain the data for a single channel and provide a 1D array of data.
When the crash occurred, it was always at the same step. The original code had 2D array input, the new data (1D array), replace array subset, and 2D array indicator (out). All arrays were numeric double.
Here are the steps to the crash:
Delete 2D array control, delete 2D array indicator, right-click 1D array (new data) and select create indicator... CRASH! It did this 3 times..
Solution: saved code after each step. No proplem since. No reboot. Code runs well.
I wouldn't have paid attention to this, but 3 consecutive crashes with same steps?? Strange...
An observation. It seemed to take forever (approx. 30 sec) to save. The program displayed "not responding" for a few seconds. It did this twice. After deleting the 2D arrays. Saving after creating the 1D indicator was instantaneous (normal). No crashes after this bizzarre episode.
The 2D array, when full contained approx 4000 elements (in total). Not that big..
11-21-2007 09:11 AM
Another update... potentially related.
It may have been caused by a faulty memory module in the PC. I removed one memory stick (down to 1GB) because the PC was in a completely frozen state this morning after simply booting and opening Outlook. Ran a memory check and it froze. Ran single module was ok. 2nd module... bad news. 😞
I was probably a bit hasty about the bug. Now I need to pickup better memory. So much for Corsair... 😠