Crash after 15-50 mins.
Crash after 15-50 mins.
for the last weak or so indigo has been crashing on my after between 15 and 50 minutes. i can't figure out why. i tried reinstalling going from 101 to 104 and the results are identical.
any ideas
I'm running Vista premium BTW and i never had this problem before
any ideas
I'm running Vista premium BTW and i never had this problem before
tried a different scene and its fine.
that really bites though, cause the crashing scene is a reno i'm working on and i'm NOT going to redo it.
i'll try the problem scene from a different camera and see if that works cause thats the last change i can remember is trying to render through a new camera angle.
that really bites though, cause the crashing scene is a reno i'm working on and i'm NOT going to redo it.
i'll try the problem scene from a different camera and see if that works cause thats the last change i can remember is trying to render through a new camera angle.
- Bogey Jammer
- Posts: 44
- Joined: Mon Aug 13, 2007 12:37 am
- Location: France
Sorry to get back this topic again but I had an Indigo crash after 10 hours of rendering (1.0.9 with vista premium 32bits). It is the first time it happened to me but I used many mesh emitters in my scene.
The questions:
The questions:
- Is there really a mesh emitter limitation? (faces or mesh?)
- Does something in the computer (eg the RAM) overflow?
- It is risky to render a very complex scene with a weak computer? (I need to render this scene for 80hours to get 8000 samples/pixels)
- Is the problem coming from something else?
I guess, that depends on your rig...zsouthboy wrote:Nonsense. I've rendered more than one scene for weeks with 32-bit builds (and FYI 32-bit build doesn't mean you can't have longs and doubles)CTZn wrote:My two cents but that could be 32 bits overflow.
Though, it's strange that such an error occurs after 10h. A RAM overflow usually happens earlier and/or gives an error message...
There shouldn't be any emitter limit.
More than likely - it's 1) a hardware problem or 2) a threading problem.
Both are plausable.
Hard problem could include drivers deciding to misbehave, or simple over heating, or a RAM stick with some soft errors that only occur when some address is accessed in a specific way.
Threading problem could be an (unintentionally) thread-unsafe portion of Indigo simply grabbing the wrong resource at the wrong time, under some very specific circumstances.
Both are plausable.
Hard problem could include drivers deciding to misbehave, or simple over heating, or a RAM stick with some soft errors that only occur when some address is accessed in a specific way.
Threading problem could be an (unintentionally) thread-unsafe portion of Indigo simply grabbing the wrong resource at the wrong time, under some very specific circumstances.
Who is online
Users browsing this forum: Ahrefs [Bot] and 107 guests