11-25-2017 03:41 PM
11-26-2017 11:55 AM
It sometimes happens to me also with CVI2015 and CVI2012. I never was able to narrow down the error to a certain situation or action.
Sometimes CVI ask me to save with the usual yes-no-cancel message that I can cancel and it keeps CVI alive (but I normally terminate my edit, save and restart; I do this when I have files with several excluded lines that I would lost is simply saving and exiting).
12-05-2017 02:01 PM
...maybe NI can elaborate on the information the address is providing...
12-15-2017 08:49 AM
Hi Wolfgang,
I looked up that address, but unfortunately it's in a very low-level function that's used extensively throughout CVI, so without more context it's impossible to know why the crash happened.
If you happen to see the problem again, and can give us a series of steps, even if the crash is rare and doesn't happen consistently, we should be able to investigate further.
Luis
12-15-2017 11:02 AM
Thank you Luis
From our local support I have learned that this error may point to a corrupt project - which I can exclude since I use this very same project frequently, and in all other situations without any problem.
This is also the good news - so far this error has hit me only once.
Of course, if it resurfaces I will try to provide extra information.
12-31-2017 05:00 AM
Hello Luis,
I am not sure if I saw the problem again or if I saw another one, because this time the address is slightly different (...46 instead of ...44).
This time it had nothing to do with switching to another project, I was working with the same project all day. The crash happened when I wanted to insert a line in source code: I have a project with several tabs open, each of these tabs refers to one of the source code files (.c, .h) of the project. I was editing in one tab, switched to another tab and wanted to insert a new line when this popup showed up:
Unfortunately, there seemed to be nothing special... so the series of steps I can give is limited to these two last actions.
Anyway, all the best!!
01-11-2018 08:18 PM
I have also seen in 2017, 2013, and 2015. It seems to happen mostly on switching tabs or the very next action. Sometimes the whole application dims and indicates it is thinking real hard. I will check the address next time it happens.