Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash after close #1776

Closed
Dmi3ryd opened this issue May 20, 2019 · 11 comments
Closed

Crash after close #1776

Dmi3ryd opened this issue May 20, 2019 · 11 comments

Comments

@Dmi3ryd
Copy link

Dmi3ryd commented May 20, 2019

Hello.

Problem

After closing the Natron a very strange error occurs, the program crashes.
This happens every time I open any project. How to fix it?

Describe the problem or suggestion here.

Natron Version 2.3.14
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)
Loading project: D:/Compose_01.ntp

Steps to Reproduce

Just open nes scene, import few images and try to close. Crash!

Versions

Natron 2.3.14
Win10 64x, 32 Ram

image

@devernay
Copy link
Collaborator

This is a known issue on windows. Once a windows developer jumps it, we may be able to better understand what happens.
It may be related to AcademySoftwareFoundation/OpenImageIO#1795 in which case it would be solved by upgrading OIIO.
Does it also crash if you build a graph without a reader or writer?

@Dmi3ryd
Copy link
Author

Dmi3ryd commented May 21, 2019

This does not happen if the project is empty.

@devernay
Copy link
Collaborator

What about a non-empty project that has neither readers nor writers: use generators instead of readers.

@Dmi3ryd
Copy link
Author

Dmi3ryd commented May 22, 2019

Generators? It's node?

@devernay
Copy link
Collaborator

generators are nodes that produce an output without an input, eg checkerboard, radial, constant, colorwheel, etc.

@Dmi3ryd
Copy link
Author

Dmi3ryd commented May 23, 2019

Not sure if this can be a good solution, because I need to work with real image files.

@devernay
Copy link
Collaborator

I'm not proposing a workaround, I'm trying to figure out the source of the bug

@Dmi3ryd
Copy link
Author

Dmi3ryd commented May 24, 2019

I think I wrote it above, right? )

@devernay
Copy link
Collaborator

Let me rephrase it: do you still get the same behavior (crash after quit) if you edit a project with only generators (see above) and no writer (only one or several viewers).

@Dmi3ryd
Copy link
Author

Dmi3ryd commented May 28, 2019

With only generators and without reades no errors!

@devernay
Copy link
Collaborator

Please re-file this issue on the right github, see #1766

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants