LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Time Machine Crashes??? (Bug?)

I just crashed LabVIEW 2012 f1 and looking at the crash report, the modification dates of all files are about 1 month in the future.

 

(The zip file itself has a modification date of 10/4/2012 11:33AM, which is correct).

 

0 Kudos
Message 1 of 11
(3,923 Views)

Wow, LabVIEW knows you are going to crash your machine in a month and premade the reports for you.  Well isn't that nice of them.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 2 of 11
(3,914 Views)

Psst, but the code is actually controlling my DeLorean. I will definitely leave it in the garage on Nov 4. 😄

0 Kudos
Message 3 of 11
(3,907 Views)

@altenbach wrote:

Psst, but the code is actually controlling my DeLorean. I will definitely leave it in the garage on Nov 4. 😄


Well- its not a bug until we can reproduce it.  So how, exactly do you crash LabVIEW?  I can't tell from your picture.

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 4 of 11
(3,894 Views)

@JÞB wrote:

@altenbach wrote:

Psst, but the code is actually controlling my DeLorean. I will definitely leave it in the garage on Nov 4. 😄


Well- its not a bug until we can reproduce it.  So how, exactly do you crash LabVIEW?  I can't tell from your picture.

 


The hardest part is reproducing it in the future...

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 5 of 11
(3,889 Views)

The file dates are independent of the crash. I looked at an earlier crash and it had the same problem with the dates.

 

In this particular case, I was working on this VI. All I did was change the upper limit of the sliders inside the array to a higher value. Bam!

(I was able to reproduce a second time, but not conistently)

 

Crash report attached.

 

 

0 Kudos
Message 6 of 11
(3,872 Views)

Seems to be an old problem....

 

Looking at a 2011SP1 crash from 6/7/2012 1:24pm shows crash files with a date of 7/7/2012 8:24.

 

Again 1 Month and 7 hours difference. (The 7 hours could be related to the time zone).

 

Somebody must have thought that January=0 and applied a correction. 😄 We need to generate a crash on December 1. to see if we get 13/1/2012. 😄

Message 7 of 11
(3,861 Views)

Looks like I might've been seeing the same thing when I had 11 installed.

 

Capture.PNG

--
Tim Elsey
Certified LabVIEW Architect
0 Kudos
Message 8 of 11
(3,849 Views)

This was reported to R&D (CAR # 377384) for further investigation.

 

BTW - Nice title, elicited a smile while dealing with a bug report.

 

Roy Smiley Happy

Message 9 of 11
(3,747 Views)

Now I am convinced this occured in the future, as NI acknowledged your post the day after the timestamp on the crash files.

Message 10 of 11
(3,737 Views)