topic Re: Annual bug thread for 2021 in BreakPoint

Annual bug thread for 2021

altenbach — Tue, 23 Feb 2021 17:46:50 GMT

Continued from the Year 2020 bug thread.

Happy New Year everyone! Hopefully we can focus again on software bugs in 2021 after dealing mostly with real ones in 2020.

The rules remain the same:

Each post here should only contain a brief description of a bug, together with a link to the thread where it is being discussed.
One post/bug!
One bug/post!
No discussion of bugs. All discussions of a bug must take place in the original linked thread.

Re: Monthly bugs for 2021

Matthew_Kelton — Wed, 10 Feb 2021 00:52:19 GMT

Scrolling while dragging in the project window no longer works (LV 2020 thru SP1)

Re: Monthly bugs for 2021

FixedWire — Tue, 23 Feb 2021 17:30:53 GMT

A VI within one library can somehow be linked to a second library and suck that second library into the dependencies. This locks up LabVIEW as it tries to figure out what to load. This one is really bad. PM me for details.

Re: Monthly bugs for 2021

thols — Fri, 26 Feb 2021 13:43:52 GMT

VI fails to compile when disabling a channel writer endpoint

Re: Annual bug thread for 2021

PNR — Mon, 19 Apr 2021 05:33:19 GMT

Potential memory corruption when (de-)serializing Sets in LabVIEW 2019 SP1 f3 (32-bit) - LabVIEW Bugs - LAVA (lavag.org)

Re: Annual bug thread for 2021

PNR — Mon, 19 Apr 2021 05:36:48 GMT

Choosing "Select XNET Database" from a XNET Frame control causes application crash when no XNET Database Aliases are defined.

CAR 1385768

Re: Annual bug thread for 2021

FixedWire — Wed, 09 Jun 2021 17:52:19 GMT

Found another terrible bug today.

The string output from 2 different VIs didn't yield an output at all (i.e. was blank) when called as a subVI.

These were rather simple VIs thankfully. Unit tested the code in question with no errors.

Approach:
1. tried to mass compile; didn't help

2. closed LV, opened LV and cleared the object cache; didn't help

3. rewired the connector pane; didn't help

4. deleted the string control, created a new control & connected the connector pane. AND IT WORKED.

This code is used in a validated environment. These types of bugs are really hard to find and can cause unexpected behavior. That's how it was found.This is an issue for risk mitigation.

Hopefully someone at NI has seen this before & can put a priority on it.

Re: Annual bug thread for 2021

wiebe@CARYA — Thu, 10 Jun 2021 07:49:19 GMT

@FixedWire wrote:

Found another terrible bug today.

The string output from 2 different VIs didn't yield an output at all (i.e. was blank) when called as a subVI.

These were rather simple VIs thankfully. Unit tested the code in question with no errors.

Approach:
1. tried to mass compile; didn't help

2. closed LV, opened LV and cleared the object cache; didn't help

3. rewired the connector pane; didn't help

4. deleted the string control, created a new control & connected the connector pane. AND IT WORKED.

This code is used in a validated environment. These types of bugs are really hard to find and can cause unexpected behavior. That's how it was found.This is an issue for risk mitigation.

Hopefully someone at NI has seen this before & can put a priority on it.

Without steps to reproduce, this will be near impossible to fix. It might even have been a user error. I know, you're absolutely sure it isn't. Without the VIs, we'll never know.

I think this thread is for bugs acknowledged by NI though...

If you can reproduce this, please create a new thread on the forum (maybe post a link to it here). When confirmed, post the BUG number here.

The rules remain the same:

Each post here should only contain a brief description of a bug, together with a link to the thread where it is being discussed.

One post/bug!

One bug/post!

No discussion of bugs. All discussions of a bug must take place in the original linked thread.

It seems I'm breaking the rules myself...

Re: Annual bug thread for 2021

thols — Thu, 08 Jul 2021 10:51:51 GMT

Delete element using CTRL+Delete only visually updates data. Actual data is not changed:

https://forums.ni.com/t5/LabVIEW/Bug-Delete-element-using-CTRL-Delete-only-visually-updates-data/m-p/4162964/highlight/false#M1201842

#1069297 LV2020 - Get Memory Status.vi

cy... — Wed, 11 Aug 2021 10:13:17 GMT

is it fixed?

Re: #1069297 LV2020 - Get Memory Status.vi

AustinManinTown — Wed, 11 Aug 2021 14:10:05 GMT

Fixed in LV2020SP1. It is not listed in the Bug Fixes:

https://www.ni.com/en-us/support/documentation/bugs/20/labview-2020-sp1-bug-fixes.html

Re: Annual bug thread for 2021

thols — Thu, 19 Aug 2021 06:46:06 GMT

Channel wire: namespace change does not update endpoint VIs

Re: Annual bug thread for 2021

thols — Tue, 24 Aug 2021 09:15:37 GMT

Channel wire probe does not work if probe is inside lvlib

Re: Annual bug thread for 2021

FixedWire — Thu, 26 Aug 2021 18:24:16 GMT

The bug surfaced again today. The noted difference was that a breakpoint after the VI had been called seems to have caused the indicator data to not be there.

Re: Annual bug thread for 2021

thols — Wed, 22 Sep 2021 07:23:58 GMT

Scale Objects While Resizing with array bugs

Re: Annual bug thread for 2021

TeraTech — Fri, 03 Dec 2021 15:39:45 GMT

Get Image of tab control is missing tabs.

Only tested in LV2017. Does not appear on known bug lists for 2017 to 2021.

Discussion here:

How to get image of entire tab control in LabVIEW - NI Community

Re: Annual bug thread for 2021

altenbach — Sat, 01 Jan 2022 17:09:58 GMT

The year 2021 is over and this thread is now closed.

Let's continue in the annual bug thread for 2022!