Jump to content

8.2.1... Argh!


Recommended Posts

Ok. I am starting to regret having upgraded to 8.2.1. It is crashing on my machines almost on a daily basis with my current applications. Before I submit a report to NI, is anybody else having problems processing *big* data files into LV and displaying it in graphs? (See attachment). After working with the resource hungry 8.0 and 8.2 series, I have a deep longing for the stability and reliability of the old LV versions... In fact, I am seriously considering downgrading to 7.1 at this point.

Regards.

Link to comment

QUOTE(Pablo Bleyer @ May 4 2007, 01:05 PM)

Ok. I am starting to regret having upgraded to 8.2.1. It is crashing on my machines almost on a daily basis with my current applications. Before I submit a report to NI, is anybody else having problems processing *big* data files into LV and displaying it in graphs? (See attachment). After working with the resource hungry 8.0 and 8.2 series, I have a deep longing for the stability and reliability of the old LV versions... In fact, I am seriously considering downgrading to 7.1 at this point.

Regards.

I suspect this won't be of any help to you at all but I'm not seeing this kind of behavior. I have experienced no crashes with 8.2.1 and that's both on XP as well as Vista platforms.

Link to comment

QUOTE(Pablo Bleyer @ May 4 2007, 01:05 PM)

Ok. I am starting to regret having upgraded to 8.2.1. It is crashing on my machines almost on a daily basis with my current applications. Before I submit a report to NI, is anybody else having problems processing *big* data files into LV and displaying it in graphs? (See attachment). After working with the resource hungry 8.0 and 8.2 series, I have a deep longing for the stability and reliability of the old LV versions... In fact, I am seriously considering downgrading to 7.1 at this point.

Regards.

Maybe some VI in your project got corrupted after the upgrade process?

Is it really related to the size of your data file (doesn't crash with smaller files)?

Go back to a previous backup of the VI or project and try to mass-compile/re-compile the project. See if it re-occurs.

Nevile.

Link to comment

QUOTE(Val Brown @ May 4 2007, 04:34 PM)

Are you working with big data sets (eg long multi-dimensional arrays, clusters)? For typical, medium sized applications I also don't have major problems. It is when I start loading relatively large amounts of data and processing (dsp filters, regressions, statistics) that it starts using a lot of memory and it crashes. Most of the time it frees the memory back to the system and my app works fine, but sometimes it just starts accumulating memory like crazy, so I guess there must be internal memory leaks or data corruption. I also think that is why I it crashes on the fpsane.cpp module generally.

Regards.

QUOTE(Neville D @ May 4 2007, 05:17 PM)

Maybe some VI in your project got corrupted after the upgrade process?

Is it really related to the size of your data file (doesn't crash with smaller files)?

Go back to a previous backup of the VI or project and try to mass-compile/re-compile the project. See if it re-occurs.

Nevile.

Don't think so. Upgraded two different systems from 8.2 to 8.2.1 and a completely new install of 8.2.1 on another. Same behavior on the three machines. It is related to the size of the files in respect to the frequency of the problem. It *has* crashed a couple of times during development, like changing the properties of some controls, but I guess that is the regular crash behavior of any application these days :-/. LV recovered correctly the VI backup on that occasions, though.

I even thought it was the version of DAQmx installed, but tried downgrading to 8.3 with the same troubles. I am also trying to avoid any express VI. They seem to use more resources than regular VIs and the crashes are more frequent when I use them.

Cheers.

Link to comment

QUOTE(Pablo Bleyer @ May 4 2007, 02:57 PM)

Don't think so. Upgraded two different systems from 8.2 to 8.2.1 and a completely new install of 8.2.1 on another. Same behavior on the three machines. It is related to the size of the files in respect to the frequency of the problem. It *has* crashed a couple of times during development, like changing the properties of some controls, but I guess that is the regular crash behavior of any application these days :-/. LV recovered correctly the VI backup on that occasions, though.

I even thought it was the version of DAQmx installed, but tried downgrading to 8.3 with the same troubles. I am also trying to avoid any express VI. They seem to use more resources than regular VIs and the crashes are more frequent when I use them.

Cheers.

I meant the VI's that you have written might be corrupted, not the vi.lib VI's.

Your comment about "LV recovered the VI backup" brings to mind a similar problem I had a while back. The so-called "recovered" VI from backup was the one that was corrupted in my case. It caused all sorts of strange crashes, till I replaced it with a same VI written from scratch.

If you remember which of these "recovered" VI's you used, I would advise just re-writing them or else obtain a copy from some old backup and modify. I'm pretty sure thats your problem.

Neville.

Link to comment

Regretfully I am having periodic crashing problems with 8.2 as well. Ihave 8.21 sitting here in its envelope waiting for the final scoop on this upgrade.

8.2 does a lot of temporarily going into not responding mode (which can sometimes recover if I go and hit windows desktop for a few secs. That kind of thing. Nothing fancy either no big data sets. Simple LV programming.

Problem is I just cant track it down to anything on my end. It happens on all three machines.

There seems to be a lot of run time (in the background of the editor) things going on. I know this isn't saying much but its so random I havn't been able to isolate it down to anything even close to specific. Man! Im just doing simple stuff here too.

Sure hope 8.2.1 is better. Got enuf on my plate ;)

Link to comment

QUOTE(John Rouse @ May 4 2007, 11:25 PM)

IMHO, if you are not having major problems with 8.2, I'd suggest that you stick with it and avoid 8.2.1. One of my reasons to update to 8.2.1 was that rings didn't allow elements out of sequence, and it was a hassle to translate ids from/to case statements. Also there are other annoying problems with controls. I've found that 8.2 is far more stable than 8.2.1.

Regards.

QUOTE(Neville D @ May 4 2007, 06:38 PM)

I meant the VI's that you have written might be corrupted, not the vi.lib VI's.

Your comment about "
LV
recovered the VI backup" brings to mind a similar problem I had a while back. The so-called "recovered" VI from backup was the one that was corrupted in my case. It caused all sorts of strange crashes, till I replaced it with a same VI written from scratch.

If you remember which of these "recovered" VI's you used, I would advise just re-writing them or else obtain a copy from some old backup and modify. I'm pretty sure thats your problem.

Neville.

I tried copying the VI contents to a new one and I still can replicate the problem. Don't know if copying everything would fix the issues, though, in the event that that is the case (maybe the error is sticky). But I don't think a corrupt VI is the problem, because I am working with several projects and have had crashes in all of them. I only used recovered backups once.

Anyway, never seen this before, but... is there a way to inspect the contents of a VI and perform a consistency check?

Regards.

QUOTE(PJM_labview @ May 4 2007, 07:02 PM)

Note: The cluster was not a type def yet.

I've also had crashes on "ThEvent.cpp" and "memory.cpp", and yes, even with tiny VIs like yours. I guess 8.2.1 was not thoroughly tested.

Regards.

Link to comment

QUOTE(Pablo Bleyer @ May 6 2007, 06:19 AM)

IMHO, if you are not having major problems with 8.2, I'd suggest that you stick with it and avoid 8.2.1. One of my reasons to update to 8.2.1 was that rings didn't allow elements out of sequence, and it was a hassle to translate ids from/to case statements. Also there are other annoying problems with controls. I've found that 8.2 is far more stable than 8.2.1.

Regards.

I tried copying the VI contents to a new one and I still can replicate the problem. Don't know if copying everything would fix the issues, though, in the event that that is the case (maybe the error is sticky). But I don't think a corrupt VI is the problem, because I am working with several projects and have had crashes in all of them. I only used recovered backups once.

Anyway, never seen this before, but... is there a way to inspect the contents of a VI and perform a consistency check?

Regards.

I've also had crashes on "ThEvent.cpp" and "memory.cpp", and yes, even with tiny VIs like yours. I guess 8.2.1 was not thoroughly tested.

Regards.

I'm just not seeing this at all and am actually quite intrigued at your report, esp re: controls. Can you post some code that consistently crashes?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.