ID 282440 - Nuke Studio crashes when a rendered EXR sequence is overwritten

Follow

Problem summary
Nuke Studio crashes when a rendered EXR sequence is overwritten

Customer reported version
nuke.10.5v2

Customer reported platform
windows10

Steps to reproduce
1) Open Nuke Studio 
2) Start a new Project
3) Import a .dpx sequence and add it to the timeline
4) Right click the track then Effects>Create Comp Special
5) In the Create Comp window select Basic Nuke Shot, change the Nuke Write node content's File Type to exr, then Create Comp
6) Right click the create comp then Render Comp 
7) Double click the rendered comp to open the Nuke script
8) In the node graph, add a Write node directly after the Read node or Reformat node, depending on Nuke Studio version
9) Copy the file path from the original Write node to the newly created one
10) Render just the first frame of the sequence
11) Switch back to the Sequence panel, Nuke Studio will crash, if not scrub the timeline, then it will crash.

Reproduced by support
This problem has been reproduced on:
Nuke 10.5v5 - Windows 10 - CentOS 6.8 - MacOSX 10.12
Nuke 10.5v1 - Windows 10
Nuke 10.0v6 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v9 - Windows 10
Nuke 9.0v7 - Windows 10 - CentOS 6.8 - MacOSX 10.12 - regression

This problem was not reproduced on:
Nuke 9.0v6 - Windows 10 - CentOS 6.8 - MacOSX 10.12
Nuke 9.0v5 - Windows 10
Nuke 9.0v1 - Windows 10
 
Earliest version tested
Nuke 9.0v1 - Windows 10 
- This issue no longer appears in this version and regressed in a version above

Expected behaviour
For Nuke Studio to not crash when the rendered comp was updated

Actual behaviour
It crashed
 
Customer crash reports:
https://crashreports.thefoundry.co.uk/crashreports/view/832291
https://crashreports.thefoundry.co.uk/crashreports/view/822641

    We're sorry to hear that

    Please tell us why