Natron Crashes on Startup

[nolanwinter]

When I try to startup Natron it crashes before opening. This happens regardless of if I'm opening an existing project or just a new project. I've tried it with both version 2.4.3 and 2.3.15. I was using Natron successfully for a few years but after taking a few months off, I can no longer get it to run.

OS: Windows 10 (64 bit) GPU: AMD Radeon RX 580 (drivers are updated)

The terminal doesn't get far before the crash: (The terminal output for version 2.4.3 is very similar.)

Copyright (C) 2013-2018 INRIA and Alexandre Gauthier-Foichat
>>>Use the --help or -h option to print usage.<<<
Info: init.py script not loaded (this is not an error)
Info: initGui.py script not loaded (this is not an error)```

[rodlie]

Probably the driver for your graphics card. Radeon OpenGL support can sometimes be a bit hit and miss. Natron can also be a bit problematic regarding OpenGL.

In general I have no issues with Intel/NVIDIA cards on Windows.

[nolanwinter]

Does that mean there isn't anything I can do? Here's more info about my drivers if that helps at all.

[fabiencollet]

I had the same issue, i remove the AMD-Software to being able to open Natron again

[nolanwinter]

I had the same issue, i remove the AMD-Software to being able to open Natron again

Are you saying you I installed the Radeon/Adrenalin software? Or is there another piece of software I'm not aware of?

[fabiencollet]

i have the same graphics card and yes I recently re-install the AMD software: pro edition, i just try to open Natron Today and after removed the AMD Software it works fine again

[lhlh1024]

“creat user interface...” after this natorn did nothing，yesterday it was ok，bug now it is broken。 then i am updata amd apu driver，natorn work again。 我很喜欢这个软件！

[lhlh1024]

After win10 update to win11,everything is OK, but Natron cann't startup. Then i'm updata amd apu driver，Natorn work again。

[soandnb]

Hello, I am also experiencing the same symptoms OP is experiencing, also with AMD graphics drivers. I was unable to get it to work on either the Windows-provided AMD driver "22Q4" or the Optional driver 22.11.1, provided by the AMD Adrenaline update utility. Both of these had a release data of November 15th. After downgrading to AMD Driver 22.5.1 (released April 28th), Natron was able to run again.

[aonphleacs]

Same problem here. Windows 10 Build 19041 with an AMD GPU and AMD Adrenaline on 22.11.2. Natron GUI fails to launch, though it can be queried from a shell.

[brunoherrera]

same here with nvidia and latest studio drivers, 3090 ti, windows 10

[devernay]

If someone with development/packaging experience on Windows wants to help, I think @rodlie would appreciate this. We need some help on:

• migrating the compiler and build dependencies from MinG-W64 to Visual C++ + vcpkg
• migrating to Qt5 (it's already working on Linux and macOS)

These may fix these driver-related crashes

[rodlie]

nvidia and latest studio drivers

I have tested on three workstations with nvidia, and I can't replicate the issue. Also runs fine on any intel. I test on Win10/Win11.

As far as I know there are no issues with v2.5 running on nvidia/intel (some odd buggy driver exists of course).

GPU issues with v2.4 vs v2.5 is an odd one. We use more or less the same software except for the toolcain (gcc/mingw).

[brunoherrera]

I no longer have this issue after uninstalling, deleting everything related to natron installation, and reinstalling. Here's a .dmp file output:

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Bruno\AppData\Local\CrashDumps\Natron.exe.9816.dmp] User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: srv* Executable search path is: Windows 10 Version 19045 MP (32 procs) Free x64 Product: WinNt, suite: SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Debug session time: Fri Dec 9 12:43:39.000 2022 (UTC - 3:00) System Uptime: 0 days 0:07:00.079 Process Uptime: 0 days 0:00:06.000 ................................................................ ................................................................ ....................................... Loading unloaded module list ......... This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (2658.260c): Access violation - code c0000005 (first/second chance not available)

+------------------------------------------------------------------------+	This target supports Hardware-enforced Stack Protection. A HW based		"Shadow Stack" may be available to assist in debugging and analysis.		See aka.ms/userhsp for more info.
dps @ssp

+------------------------------------------------------------------------+

For analysis of this file, run !analyze -v ntdll!NtWaitForMultipleObjects+0x14: 00007fff`f258dc14 c3 ret 0:000> !analyze -v

---

• *
• Exception Analysis *
• *

  ---

Unable to load image C:\Program Files\Natron\bin\QtCore4.dll, Win32 error 0n2 *** WARNING: Unable to verify timestamp for QtCore4.dll

KEY_VALUES_STRING: 1

Key  : AV.Dereference
Value: NullClassPtr

Key  : AV.Fault
Value: Read

Key  : Analysis.CPU.mSec
Value: 843

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 60626

Key  : Analysis.IO.Other.Mb
Value: 38

Key  : Analysis.IO.Read.Mb
Value: 2

Key  : Analysis.IO.Write.Mb
Value: 47

Key  : Analysis.Init.CPU.mSec
Value: 562

Key  : Analysis.Init.Elapsed.mSec
Value: 142353

Key  : Analysis.Memory.CommitPeak.Mb
Value: 152

Key  : Timeline.OS.Boot.DeltaSec
Value: 420

Key  : Timeline.Process.Start.DeltaSec
Value: 6

Key  : WER.OS.Branch
Value: vb_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1

Key  : WER.Process.Version
Value: 1.0.2.21

FILE_IN_CAB: Natron.exe.9816.dmp

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr) rax=0000000000000000 rbx=000000bddf1fb188 rcx=000000bddf1fb108 rdx=0000000000000000 rsi=000002b6d8874910 rdi=000000bddf1fb108 rip=00007fffbd11eaee rsp=000000bddf1fb020 rbp=0000000000000000 r8=00000000ffffffff r9=0000000000000001 r10=000002b6cbdb0000 r11=000000bddf1faf40 r12=0000000000000000 r13=000000bddf1fb188 r14=000000bddf1fb2d0 r15=000000bddf1fb180 iopl=0 nv up ei pl nz na pe cy cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010203 QtNetwork4+0xaeaee: 00007fffbd11eaee 488b4208 mov rax,qword ptr [rdx+8] ds:0000000000000008=???????????????? Resetting default scope

EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007fffbd11eaee (QtNetwork4+0x00000000000aeaee) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000008 Attempt to read from address 0000000000000008

PROCESS_NAME: Natron.exe

READ_ADDRESS: 0000000000000008

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000008

STACK_TEXT:
000000bddf1fb020 0000000000000000 : 000000bddf1fb188 000002b6d8874910 000000bddf1fb108 000000bddf1fb208 : QtNetwork4+0xaeaee

STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: QtNetwork4+aeaee

MODULE_NAME: QtNetwork4

IMAGE_NAME: QtNetwork4.dll

FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_QtNetwork4.dll!Unknown

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 4.8.7.0

FAILURE_ID_HASH: {c5a5d181-f41e-7e6c-fe07-63edf6a45b27}

Followup: MachineOwner

[rodlie]

@brunoherrera Thanks for the report, I found the issue!

The check for updates during startup is what crashes Natron.

[rodlie]

Workaround (will delete your config) until fixed: https://github.com/rodlie/natron-addons/blob/main/tools/clearConfig.bat

Then start Natron and answer no when asked to check for updates during startup.

[soandnb]

Workaround (will delete your config) until fixed: https://github.com/rodlie/natron-addons/blob/main/tools/clearConfig.bat

Then start Natron and answer no when asked to check for updates during startup.

I believe this to be a separate crash, unrelated to the AMD drivers crash.

As of right now, I'm currently running older AMD drivers, and am able to launch 2.4.4 and 2.5 without any issues (the latter assuming I keep Check for Updates turned off). If I upgrade to the latest AMD drivers, neither version will start (2.4.4 will crash after the "starting user interface..." message, and 2.5 will simply appear to not start at all).

I would suggest, for AMD graphics users, to attempt downgrading to an older version of the AMD driver suite. In my personal experience, I was able to get Natron working with a driver-only install of 22.5.1 (though I have not tested full or minimal installs with Adrenaline).

[rodlie]

I believe this to be a separate crash, unrelated to the AMD drivers crash.

Yes, this issue got kind of hijacked, sorry about that.

The check for updates issue affects all Windows users, and will be fixed as soon as possible (this weekend).

The AMD issue is out of our control, so the only thing we can do is to recommend the version you mention. We should add that to known issues (and maybe add recommended driver version on our website).

When we move to Qt5 our compatibility with AMD may improve, but that's just a theory. I will start working on the Windows Qt5 port in about a week.

[brunoherrera]

sorry too people, I thought it was the drivers too so I didn't want to make a new issue

[rodlie]

I updated the Windows build with a fix for the qt+openssl issue, will probably not fix any AMD issues, but for anyone else with similar issues the new build might fix it.

https://github.com/NatronGitHub/Natron/releases/download/v2.5.0/Natron-2.5.0-Windows-x86_64.zip SHA256 checksum: caed0b649ff2515b963f0b4fc009eb451a41d8ba3d6e5d4260253dd9e104c517

[brunoherrera]

I formated my pc a few days ago, I opened my project and worked flawlessly, rendered correctly and stuff, that was a few days ago, now I open the project again and I'm having the same issue "Shadertoy1: Can not render: glGetString(GL_VERSION) failed." but in preferences gpu rendering everything shows correctly except "Max. Memory: Unknown"

the weird thing is that it worked perfectly the first time I launched, and now it doesn't, even after cleaning stuff with the script from rodlie

I just don't know what else to do, this is very sad

EDIT: I tried it inside windows sandbox given that it worked with a clean system like I mentioned, gave an error that the driver didn't support opengl (obvious, because it's basically a VM) so before throwing the towel I installed the opengl legacy thing (OpenGL Software Renderer (FOR LEGACY HARDWARE ONLY)) and it worked, multiple times, I'll try installing the legacy thing in my PC (not sandbox) and will edit again with the results, I think it should work

EDIT 2: it worked :D

EDIT 3: now it's skipping frames (black frames in between) (but seems to be another thing, if I re open the project it get's fixed, maybe is just some weirdness with opengl being an old version? does it when I use GMIC

[soandnb]

The AMD issue is out of our control, so the only thing we can do is to recommend the version you mention. We should add that to known issues (and maybe add recommended driver version on our website).

I believe I have found another workaround related to AMD drivers issue. In Natron/bin/mesa there is a file called opengl32.dll. Move that file from Natron/bin/mesa to Natron/bin, and Natron should run with Software Rendering.

I have a counterfeit card to thank for this discovery. Normal AMD drivers were unable to run on it, so it reverted to generic Windows video drivers. Attempting to open Natron with these generic drivers failed to launch, but gave me a splash screen that directed me to do the above, at which point Natron was able to start up and display, both on the generic drivers and on the formerly busted AMD drivers.