ID 462543 - Katana crashes when committing a smaller parameter array widget size by clicking on a parameter element that would no longer exist

Follow

Problem summary
Katana crashes when reducing a parameter array field then committing by clicking on a parameter array input field that would be non-existent after parameter arrays are resized.

Customer reported version
4.0__4.0v1

Customer reported platform
centos7

Steps to reproduce

1) Create an AttributeSet node

2) Set the numberValue parameter of the AttributeSet node to a 1x2 array.

3) Once this have been committed, edit the column value, changing it to 1 (giving a 1x1 array), then commit it by clicking on the right-most parameter array input field.



Expected behavior
The numberValue parameter array is committed to the correct size. 

Actual behavior
Katana crashes.

Workaround
When committing a reduced parameter array size, do not click in an input parameter field. 

Reproduced by support
This crash has been reproduced in:
Katana 4.0v1 - CentOS 7
Katana 3.6v3 - CentOS 7
Katana 3.6v1 - CentOS 7
Katana 3.5v4 - CentOS 7
Katana 3.5v1 - CentOS 7
Katana 3.2v6 - CentOS 7
Katana 3.1v1 - CentOS 7
Katana 3.0v9 - CentOS 7, Windows 10
Katana 3.0v1 - CentOS 7, Windows 10
Katana 2.5v1 - CentOS 7, Windows 10

Unable to reproduce crash, but error is thrown in:

[ERROR python.root]: A RuntimeError occurred in "GlobalEventFilter.py": wrapped C/C++ object of type InputLineEdit has been deleted    Traceback (most recent call last):      File "python/UI4/App/Application.py", line 155, in notify      File "python/UI4/software_python/QT4Widgets/v0/GlobalEventFilter.py", line 228, in eventFilter    RuntimeError: wrapped C/C++ object of type InputLineEdit has been deleted
Katana 2.2v2 - CentOS 7
Katana 2.2v1 - CentOS 7

Unable to reproduce bug in:
Katana 4.0v1 - Windows 10
Katana 3.6v3 - Windows 10
Katana 3.6v1 - Windows 10
Katana 3.5v4 - Windows 10
Katana 3.5v1 - Windows 10
Katana 3.2v6 - Windows 10
Katana 3.1v1 - Windows 10
Katana 2.0v1 - CentOS 7

Earliest version tested
Katana 2.0v1 - This issue doesn't appear in this version and has regressed

    We're sorry to hear that

    Please tell us why