LabVIEW 2012 crashes on different File Open/Save dialogs, if last working directory no longer exists

[instrumento]

On several Windows 7, 64 bit machines, if I open LV2012 SP1 f1 64 bits, create a VI and save it on a directory, exit LabVIEW, delete the directory where I saved the VI, restart LabVIEW and do a File/Open, LabView goes puff and disappears.

Sometimes it happens on File/Save As.  To fix this I have to double click on an existing VI on Explorer, save it, and then after exiting and restarting LabVIEW I can do File Open again.

I do have Classic Shell installed on all the systems, but even after uninstalling it and rebooting the machine, the behavior is the same.

I tried removing the file from the list of last opened files in LabVIEW.ini but that doesn't do the trick.

[ShishKeBobby]

Hi instrumento,

Was there an error associated with the crash, or did LabVIEW crash without an error message?

Thanks,

[instrumento]

LabVIEW simply disappears.

Note that I delete from the start directory the nierrxxx stuff the installation drops in there, not sure those would have catched and displayed something.

I have a bunch a of directories in documents\labview data\lvinternalreports\labview\1.0.1f1 (64 bit) each with one or more .dmp file in them, but I'm not sure they are realated (need to clean them all and replicate the problem to make sure).

[ShishKeBobby]

Hi instrumento,

I'm very interested in getting this issue reproduced on my end.  Would it be possible for you to post your code along with some instructions on how to reproduce the error?

Thanks,

[instrumento]

Not sure if this is related or something else, however I now have a VI on my desktop that if I double click on it brings up LV 12.0.1f3/64, which opens and shows me the file.  If I then do File/Save As/Rename and hit Continue, LV crashes.

Error is: Exception: Access violation (0xC0000005) at EIP=0x000007FEFC2DE3C4.  I have an about 200 KB dump file if anyone wants it, as the Send button on my error report is disabled and help just tells me to contact my administrator, which is me (and I configured the VLM to allow users to do that, stop and restarted the VLM but still no go).

Lvlog.txt is

----------------

####
#Date: Wed, Aug 21, 2013 3:27:32 PM
#OSName: Windows 7 Enterprise Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: LabVIEW
#Version: 12.0.1f3 64-bit
#AppKind: FDS
#AppModDate: 05/29/2013 21:55 GMT
#LabVIEW Base Address: 0x0000000140000000



<DEBUG_OUTPUT>
8/21/2013 3:27:41.720 PM
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash 0x0: Crash caught by NIER
minidump id: 71bcb82e-95ba-41ca-884d-efe3b7fc1779
ExceptionCode: 0xC0000005�r

</DEBUG_OUTPUT>
0x0000000141DBE41B - LabVIEW <unknown> + 0
0x0000000141DBEA62 - LabVIEW <unknown> + 0
0x0000000019C47D1B - <unknown> <unknown> + 0
0x000000000293A7E0 - <unknown> <unknown> + 0
0x0000000000424FB0 - <unknown> <unknown> + 0
0x0000000001000000 - <unknown> <unknown> + 0
0x000000000000000F - <unknown> <unknown> + 0

[instrumento]

If I then copy that file to another directory, and try to do the same thing, I can get past the "continue" button and the File Dialog pops up.  I can do that whether I tell it to ignore all VIs it can't find, as the relative path changed, or if I go and find the one that is needed to re-establish the relative paths.

If I go back and open the original file in the Desktop, and attempt a save as/rename, LV crashes.

The files are identical, as compared over SMB with Unix's cmp.

[Prickly_Pear]

I believe that this error has something to do with the particulars of your current system. Some of the documentation on the internet about this error code describes an error concerning the memory. It can be difficult to pin down the root of the problem because it is difficult to reproduce on a different computer. Try reading more about it on some computer forums. This one might be helpful http://stackoverflow.com/questions/5303524/what-exactly-is-the-scope-of-access-violation-0xc0000005. Please note that this link will take you away from ni.com an onto an external site that we do not maintain.

Jeremy P.

[instrumento]

0xc0000005 is an acess violation, sigsegv in most cases,  users can't find what causes it without the source code, or a lot of detective wok.

LV is doing something wrong when calling the file save dialog. Nothing else seems to be funny in my system, no other application crashes.  But just open that file on a fresh LV session, and trying to do a file save as rename operation, and LV crashes every single time.