{"action":"created","issue":{"url":"https://api.github.com/repos/MrKepzie/Natron/issues/1474","repository_url":"https://api.github.com/repos/MrKepzie/Natron","labels_url":"https://api.github.com/repos/MrKepzie/Natron/issues/1474/labels{/name}","comments_url":"https://api.github.com/repos/MrKepzie/Natron/issues/1474/comments","events_url":"https://api.github.com/repos/MrKepzie/Natron/issues/1474/events","html_url":"https://github.com/MrKepzie/Natron/issues/1474","id":186086821,"number":1474,"title":"Crashes while rendering...","user":{"login":"Chromatamata","id":23139963,"avatar_url":"https://avatars.githubusercontent.com/u/23139963?v=3","gravatar_id":"","url":"https://api.github.com/users/Chromatamata","html_url":"https://github.com/Chromatamata","followers_url":"https://api.github.com/users/Chromatamata/followers","following_url":"https://api.github.com/users/Chromatamata/following{/other_user}","gists_url":"https://api.github.com/users/Chromatamata/gists{/gist_id}","starred_url":"https://api.github.com/users/Chromatamata/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Chromatamata/subscriptions","organizations_url":"https://api.github.com/users/Chromatamata/orgs","repos_url":"https://api.github.com/users/Chromatamata/repos","events_url":"https://api.github.com/users/Chromatamata/events{/privacy}","received_events_url":"https://api.github.com/users/Chromatamata/received_events","type":"User","site_admin":false},"labels":[{"id":398280496,"url":"https://api.github.com/repos/MrKepzie/Natron/labels/func:engine","name":"func:engine","color":"fbca04","default":false},{"id":481093521,"url":"https://api.github.com/repos/MrKepzie/Natron/labels/info:feedback-needed","name":"info:feedback-needed","color":"5319e7","default":false},{"id":38672335,"url":"https://api.github.com/repos/MrKepzie/Natron/labels/type:bug","name":"type:bug","color":"d93f0b","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2016-10-29T16:18:40Z","updated_at":"2016-12-14T13:49:00Z","closed_at":null,"body":"Please ask questions (\"how do I...?\") on the [forum](http://forum.natron.fr), not by filing issues.\n\nMake concrete suggestions for fixing the code (\"here is a patch\") by filing\na [pull request](https://github.com/MrKepzie/Natron/pull/new/master), not an issue.\n\nHi. I love Natron but I have a really severe problem. The program crashes nearly every time during a render. The crashes are random. Ie. They never occur at the same place in the render process. It can be at anywhere from 0% through to 99%. Very very occasionally, renders complete to 100% but it has only happened a few times. It mostly just crashes. I have tried using many different codecs and different container files. I doesn't help. I have tried moving all the files involved in the project onto the computer's main hard drive. It doesn't help. I have tried installing Natron and rendering on a second computer. It doesn't help. I have tried installing the latest version of Natron and I have also tried  using previous versions. It doesn't help. It seems to be worse, the more complex the nodal structure and the longer, therefore the render time. The problem is so bad that I cannot use Natron as an effective rendering tool... which is sad because I would like to. If it would just render it would be AMAZING! Both computers that I have tried had Windows 7 installed. I have tried using Natron 2.1.2, 2.1.6 and 2.1.7.\n### Problem\n\nDescribe the problem or suggestion here.\n\n**Expected behavior:** [What you expected to happen]\n\n**Actual behavior:** [What actually happened]\n- If your problem is a crash in an official release/snapshot, please include verbose output from the application\n  from a terminal if possible.  If you also submitted a crash report, indicate the CrashID if possible.\n- If you need to report a compilation issue, please create a [gist](https://gist.github.com)\n  that contains the _full_ verbose build log.\n- If your problem is a crash in a build that you made yourself, please create a [gist](https://gist.github.com)\n  that contains a _full_ backtrace.\n### Steps to Reproduce\n1. [First Step]\n2. [Second Step]\n3. [and so on...]\n\nYou may submit a link to any screenshots/videos that can be used to understand how to reproduce the issue.\n### Versions\n- **Natron version/commit** (they can be retrieved from the About Window): \n- **OS version:** \n"},"comment":{"url":"https://api.github.com/repos/MrKepzie/Natron/issues/comments/267037959","html_url":"https://github.com/MrKepzie/Natron/issues/1474#issuecomment-267037959","issue_url":"https://api.github.com/repos/MrKepzie/Natron/issues/1474","id":267037959,"user":{"login":"Chromatamata","id":23139963,"avatar_url":"https://avatars.githubusercontent.com/u/23139963?v=3","gravatar_id":"","url":"https://api.github.com/users/Chromatamata","html_url":"https://github.com/Chromatamata","followers_url":"https://api.github.com/users/Chromatamata/followers","following_url":"https://api.github.com/users/Chromatamata/following{/other_user}","gists_url":"https://api.github.com/users/Chromatamata/gists{/gist_id}","starred_url":"https://api.github.com/users/Chromatamata/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Chromatamata/subscriptions","organizations_url":"https://api.github.com/users/Chromatamata/orgs","repos_url":"https://api.github.com/users/Chromatamata/repos","events_url":"https://api.github.com/users/Chromatamata/events{/privacy}","received_events_url":"https://api.github.com/users/Chromatamata/received_events","type":"User","site_admin":false},"created_at":"2016-12-14T13:48:59Z","updated_at":"2016-12-14T13:48:59Z","body":"Ok... I want to give you another update that may help get to the bottom of this problem. I have managed to work around this problem in a very laborious way. My project was just over 4500 frames long. If I divide my project into lengths of 1000 or less then join the resulting files together later losslessly using external software, I am usually able to get through a render without a crash even with the simultaneous thread set to 4! (Not always but usually). In other words, none of the information being processed by Natron is causing a crash nor is the processing of any particular part of my project too data intensive for Natron to handle. As a programmer, myself, I would have to conclude, therefore that the likely cause of this problem is a memory leek. The longer the program runs and processes data, the more likely it is to crash... so something isn't being tidied up properly in memory. If that is the case, the trouble with that, as I'm sure you're aware, is that it may or may not be your fault. It may be some poor handling of memory you have programmed in by accident or it may well be something the language you are writing Natron in causes by itself or it could even be something Windows is doing wrong with the allocation of memory resources. Most people may not be encountering this problem as most people may be using the Linux or Mac version of your program which may implicate Windows as being at fault. If it is a memory leek and it isn't your own code's fault... it probably won't be possible to fix this. I hope I'm wrong as I LOVE NATRON. In fact, I may be addicted to it and want to continue using it without all these extra time consuming steps. :-)"}}
{"actor":{"display_login":"Chromatamata"}}