ID 510160 - Nuke errors with std::bad_alloc or crashes when loading a Nuke script with nuke.tcl('load ffmpegReader') or nuke.tcl('load ffmpegWriter') in an onScriptLoad callback on AMD CPUs

Problem summary
On a Linux system with an AMD CPU, Nuke errors with std::bad_alloc when calling nuke.tcl('load ffmpegReader') or nuke.tcl('load ffmpegWriter') from an onScriptLoad callback.
 
On a Windows system with an AMD CPU, this instead manifests as a crash that only occurs when calling nuke.tcl('load ffmpegReader') from an onScriptLoad callback and produces the following error:

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ Crash address: 0x214 Assertion: Unknown assertion type 0x00000000 Thread 0 (crashed)  0  atio6axx.dll + 0x1a0091b  1  atio6axx.dll + 0x19fa3e3  2  0x7ffd9f290000  3  atio6axx.dll + 0x19f52a3  4  0x7ffd9f290000  5  atio6axx.dll + 0x19f89fe  6  atio6axx.dll + 0xbcae11

 
Customer reported version
Nuke 13.1v1
 
Customer reported platform
SUSE
 
Steps to reproduce
 
1) Load a Nuke script that contains an onScriptLoad callback which calls nuke.tcl('load ffmpegReader')
 
 
Expected behaviour
ffmpegReader is loaded successfully on script load
 
Actual behaviour
std::bad_alloc error on Linux
 
Crash and EXCEPTION_ACCESS_VIOLATION_READ on Windows
 
Workaround
For the affected scripts, remove nuke.tcl('load ffmpegReader') or nuke.tcl('load ffmpegWriter') from the onScriptLoad callback in the Root/Python tab.
NOTE: The callbacks are included by default when exporting scripts from Nuke Studio/Hiero.
 
Reproduced by Support in:
Nuke 13.2v1 - Ubuntu 22.04, Windows 10