forwarded 486878
http://lists.blender.org/pipermail/bf-committers/2008-June/021296.html
thanks
Mikko Rasa <[EMAIL PROTECTED]> (18/06/2008):
> That was a piece of cake since I have experimental in my sources.list
> already. As for results, the bug is still present in 2.46+dfsg-1.
Thanks.
> I to
Cyril Brulebois wrote:
Mikko Rasa <[EMAIL PROTECTED]> (18/06/2008):
In my opinion, the problem is not in the infinite-timeout select but
in the fact that blender seems to increment the next autosave time
instead of setting it to current time plus interval.
Hi,
thanks for your analysis. Before
Mikko Rasa <[EMAIL PROTECTED]> (18/06/2008):
> In my opinion, the problem is not in the infinite-timeout select but
> in the fact that blender seems to increment the next autosave time
> instead of setting it to current time plus interval.
Hi,
thanks for your analysis. Before I forward it to the
Package: blender
Version: 2.45-5+b1
Severity: normal
Occasionally, blender enters a select() with a NULL timeout, waiting for
events from the X server. If this happens when it's inactive for a
prolonged time, autosaves get "queued up" and are processed at once when
the select finishes (due to ble
4 matches
Mail list logo
