ID 280582 - Group node with empty postage stamp crashes Nuke after clearing and re-opening a script

Follow

Problem summary:
The user has created an empty Read node that is embedded inside a group node with Postage Stamp enabled.  When the user deletes the Group node, clears their current Nuke script and then attempts to open a recent comp, Nuke crashes.

Customer reported version:
nuke.10.5v1

Customer reported platform:
n_a_linux

Steps to reproduce:
 
1 - create a Read node, clear the file path
2 - group the Read node
3 - Turn postage stamps on the Group node
4 - Delete the Group node
5 - Clear the script
6 - Choose File > Open Recent Comp > and pick a file
Result - Nuke will crash and display a crash report
 

Workaround:
Instead of 'Clear' Nuke or 'Close Comp', It's recommended the user 'Quit's Nuke and reopens a recent comp in a new window.

Reproduced by support

Crashes:
Nuke 10.5v4 - Windows 7 - MacOSX 10.12 - CentOS 6.9
Nuke 10.5v1 -  Windows 7 - MacOSX 10.12 - CentOS 6.9
Nuke 10.0v6 - Windows 7
Nuke 10.0v1 - Windows 7
Nuke 9.0v9 - Windows 7
Nuke 9.0v1 - Windows 7 - MacOSX 10.12 - CentOS 6.9

Working:
Nuke 8.0v7 - Windows 7 - MacOSX 10.12 - CentOS 6.9

Expected behaviour:
Opening a recent comp after deleting a group node that contains an empty read node with an enabled postage stamp, should open the script without crashing

Actual behaviour:
Nuke crashes and displays an error report after deleting a group node that contains an empty read node with an enabled postage stamp then clears the project and loads a new scene.

    We're sorry to hear that

    Please tell us why