ID 376558 - Nuke gets caught in a loading loop if a semi-colon is placed within the OFX_PLUGIN_PATH environment variable

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Nuke

Problem summary
Users have found that if they accidentally have a semi-colon within their OFX_PLUGIN_PATH environment call, Nuke will get stuck in a loop when opened.
This loop delays Nuke's opening time triple or more than normal.

This issue is most prevalent on Windows, it does occur on Linux and Mac, but only on the first launch. 

Customer reported version
nuke.11.2v5

Customer reported platform
windows7

Steps to reproduce

1) Open a Command Prompt window

2) Within the Command Prompt window, execute the following:

Windows:

set OFX_PLUGIN_PATH=;/test/path/here

Linux, Mac:  ( Must be existing path )

export OFX_PLUGIN_PATH=";/home"

3) Launch Nuke within the Command Prompt window.

Result: Nuke will get stuck in a plugin loading loop and not launch for a while

  This issue only occurs the first time on Mac and Linux, this may be due to the differences in setting environment variables.


Workaround
If the issue occurs, check your OFX_PLUGIN_PATH environment variable for the semi-colon mistake and remove it.

Reproduced by support

This bug has been reproduced in:
Nuke11.3v1- Windows 7 - Mac10.13 - CentOS7
Nuke11.2v1 - Windows 7
Nuke11.1v1 - Windows 7
Nuke11.0v1 - Windows 7
Nuke10.5v1 - Windows 7
Nuke10.0v1 - Windows 7
Nuke9.0v1 - Windows 7
Nuke8.0v1 - Windows 7 - Mac10.13 - CentOS7

Earliest version tested
- This issue appears to be in all versions of the product

Expected behaviour
Nuke should load without issues

Actual behaviour
Nuke gets caught in an environment variable loading loop

    We're sorry to hear that

    Please tell us why