Access Violation

[Roger Ohlund]

Hi !

I have an application that delivers 12 sets of data with 54 items in each
set.
I wanted to build a history presentation VI, so I initialized a
3-dimensional matrix with 12*54*300 values.
Using extract array subset and replace array subset I shift the the 300
values 1 step each time the main application has delivered the data.
At any given time I can access any of the 12*54 arrays with its 300 values
with a little help of some useful VI's.
Anyhow, The VI works nicely, but the main application that earlier ran for
days in a row, suddenly has started to give access violation errors and the
whole LabView environment shuts down.
I've checked the memory usage with the system manager, and no memory loss.

I'm at loss. Anyone with an idea ?

Yours/

--
R
oger Ohlund, MSc Engineering Physics
Ericsson Erisoft AB
(S?/EPL/J/T) Ph: +46 910 731423
Skelleftehamnsvagen 206 Cell: +46 70 2648301
S-932 83 Ursviken, Sweden Fax:
mailto:Roger.Ohlund@epl.ericsson.se

[Peter Klapka]

Roger,

Are any of your "Useful VI's" making DLL calls? I've found that LabView
takes a dive or starts behaving strangely if you don't "allocate" enough
memory space for their input parameters. If this is the case, you may want
to make sure you aren't trying to squeeze an extra ellement or two somewhere
in the array. You might check your indexing (0 vs 1) etc.

~Petr~


"Roger Ohlund" wrote in message
news:a3m9tt$k38$1@antares.lu.erisoft.se...
> Hi !
>
> I have an application that delivers 12 sets of data with 54 items in each
> set.
> I wanted to build a history presentation VI, so I initialized a
> 3-dimensional matrix with 12*54*300 values.
> Using extract array subset and replace array subset I shift the the 300

> values 1 step each time the main application has delivered the data.
> At any given time I can access any of the 12*54 arrays with its 300 values
> with a little help of some useful VI's.
> Anyhow, The VI works nicely, but the main application that earlier ran for
> days in a row, suddenly has started to give access violation errors and
the
> whole LabView environment shuts down.
> I've checked the memory usage with the system manager, and no memory loss.
>
> I'm at loss. Anyone with an idea ?
>
> Yours/
>
> --
> Roger Ohlund, MSc Engineering Physics
> Ericsson Erisoft AB
> (S?/EPL/J/T) Ph: +46 910 731423
> Skelleftehamnsvagen 206 Cell: +46 70 2648301
> S-932 83 Ursviken, Sweden Fax:
> mailto:Roger.Ohlund@epl.ericsson.se
>
>

[Roger Ohlund]

Hi!

Actually I'm not using any external DLL's, BUT somehow it feels like if I
was adressing areas that I shouldn't.
(The last conclusion I've drawn from the DrWatson log file.)
No, the only VI's used are standard VI's from National Instrument.
However, I've recently found that decreasing the size of this 3-D array
actually can remove my problems.
I don't like the feeling of this my latest finding, can there be something
wrong with LabView ?

Yours/

--
Roger Ohlund, MSc Engineering Physics
Ericsson Erisoft AB
(S?/EPL/J/T) Ph: +46 910 731423
Skelleftehamnsvagen 206 Cell: +46 70 2648301
S-932 83 Ursviken, Sweden Fax:
mailto:Roger.Ohlund@epl.ericsson.se
Peter Klapka wrote in message ...
>Roger,
>
> Are any of your "Useful VI's" making DLL calls? I've
found that LabView
>takes a dive or starts behaving strangely if you don't "allocate" enough
>memory space for their input parameters. If this is the case, you may want
>to make sure you aren't trying to squeeze an extra ellement or two
somewhere
>in the array. You might check your indexing (0 vs 1) etc.
>
>~Petr~

[Ben]

Hi Roger,

Would it be possible to post an example that demonstrates the problem?

What do you mean by "delivered the data"?

Waht vesrion of LabVIEW are you using?

Ben