ID 359684 - Studio crashes when building time lines from xmls and doing basic workflow

Follow

Problem summary
While building the sequences for review, Nuke Studio is Segmentation Faulting crashing. This happens randomly while working in Studio doing basic workflows of importing XMLs of movs and exrs.

Customer reported version
nuke.11.1v4

Customer reported platform
centos7

Steps to reproduce

  1. Download all XMLs attached and put in location to use later
  2. Launch Nuke Studio
  3. Start new project
  4. Use the shortcut ctrl + shift + alt + I to import an XML you downloaded ( any of the xmls except gG*)
  5. Right click above the track > New Track from XML - import three other XMLs ( any of the xmls except gG*)
  6. Now have four tracks in sequence
  7. Create a new track from XML ( any of the xmls except gG*)<--- while doing this it might crash
  8. Set a track to over blend mode
  9. Right click on a track  item > Effects >Transform
  10. Set scale and transform to have track sit above the track below it in the left corner
  11. Copy soft effect to all other clips on the track with the blend mode
  12. Right click above all clips > New Track > New Track from XML
  13. Bring in the gG* XML ( exr files)
  14. Cache the timeline - try with timeline disk caching and localisation

  15. Playback the timeline

  16. Scrub through the timeline

  17. Add in and out points using the hot keys

  18. Create a comp from a few clips - add a roto, grade to the different clips

  19. Version the clips

  20. Repeat the steps from step 3 for a while <--- crash will happen after a while of doing these steps over and over.

    - do these quite quickly, it will usually crash when working at a quicker speed then when working slowly.

Shorter repro steps from Dan M:

Import XMLs as new tracks into a sequence twice. Right clicking on the clip created by the first XML in the bin should cause the crash.

Reproduced by support
Reproduced by QA

Expected behaviour
Nuke Studio to work as normal

Actual behaviour
It crashes

    We're sorry to hear that

    Please tell us why