|
 |
Chris Cason wrote:
> unless I can reproduce it then it's unlikely to be fixed.
>
> if you can send me a scene file that will reliably cause the error on W2K or XP
> then I can find the cause.
>
> -- Chris
Hmm. Half the problem is it happens in a completely non-deterministic
fashion. The only thing you can hope to do is add some basic thread
synchronisation to the code that deals with the file handle, From what I
have experienced, there is no single way to cause this problem to
reproduce.
Post a reply to this message
|
|
|
|
Michael Raiford <mra### [at] hotmail com> wrote:
> Chris Cason wrote:
>
>
> > unless I can reproduce it then it's unlikely to be fixed.
> >
> > if you can send me a scene file that will reliably cause the error on W2K or XP
> > then I can find the cause.
> >
> > -- Chris
>
> Hmm. Half the problem is it happens in a completely non-deterministic
> fashion. The only thing you can hope to do is add some basic thread
> synchronisation to the code that deals with the file handle, From what I
> have experienced, there is no single way to cause this problem to
> reproduce.
That's my experience, too. It seems to arise most reliabily if there's a
parse error when there's a main scene file calling macros in an include
file -- but I can't say if that's really a symptom, or if it's just that
most of my code lives in other files.
Sometimes it just happens -- even if the parse is over and had no errors.
Post a reply to this message
|
|
