POV-Ray : Newsgroups : povray.general : Operation timed out? (Win3.7 RC3 Server Time
1 Nov 2024 19:16:01 EDT (-0400)
  Operation timed out? (Win3.7 RC3 (Message 1 to 3 of 3)  
From: gregjohn
Subject: Operation timed out? (Win3.7 RC3
Date: 13 Feb 2011 17:00:00
Message: <web.4d58543fe4e81b7434d207310@news.povray.org>
I set up an animation of 36 frames, each which was taking ~20 minutes to render.
When I returned hours later, I saw that the render bombed for a message of
"Operation timed out."  The screen was highlighting an include statement.  I
hadn't touched the PC, so the "timed out" shouldn't have been different from
frame to frame.


Copy Pane below:


Animation Options
  Initial Frame:        1  Final Frame:       36
  Frame Step:           1
  Initial Clock:    0.000  Final Clock:    0.000
  Cyclic Animation.....Off  Field render.........Off  Odd lines/frames.....Off
Image Output Options
  Image resolution.....500 by 500 (rows 1 to 500, columns 1 to 500).
  Output file..........C:\$user\pfa_demo\gini\subsurf_mh_f11j32.png, 24 bpp PNG
  Dithering............Off
  Graphic display......On  (gamma: sRGB)
  Mosaic preview.......Off
  Continued trace......Off
Information Output Options
  All Streams to console..........On
  Debug Stream to console.........On
  Fatal Stream to console.........On
  Render Stream to console........On
  Statistics Stream to console....On
  Warning Stream to console.......On


clock 0.886  seconds 1.33 frame    32  ff/24 1.50  clock*80  70.8571
-
"C:\$user\pfa_demo\gini\subsurf_mh_f11j.pov" line 39: Parse Error: Operation
timed out.

Render failed
-
CPU time used: kernel 21.41 seconds, user 40087.44 seconds, total 40108.84
seconds.
Elapsed time 24616.95 seconds, CPU vs elapsed time ratio 1.63.
----------------------------------------------------------------------------


Post a reply to this message

From: Le Forgeron
Subject: Re: Operation timed out? (Win3.7 RC3
Date: 14 Feb 2011 12:22:08
Message: <4d5964c0$1@news.povray.org>
Le 13/02/2011 22:59, gregjohn nous fit lire :
> I set up an animation of 36 frames, each which was taking ~20 minutes to render.
> When I returned hours later, I saw that the render bombed for a message of
> "Operation timed out."  The screen was highlighting an include statement.  I
> hadn't touched the PC, so the "timed out" shouldn't have been different from
> frame to frame.

> clock 0.886  seconds 1.33 frame    32  ff/24 1.50  clock*80  70.8571
> -
> "C:\$user\pfa_demo\gini\subsurf_mh_f11j.pov" line 39: Parse Error: Operation
> timed out.
> 
> Render failed
> -
> CPU time used: kernel 21.41 seconds, user 40087.44 seconds, total 40108.84
> seconds.
> Elapsed time 24616.95 seconds, CPU vs elapsed time ratio 1.63.
> ----------------------------------------------------------------------------

Without presuming of the windows port, there is a single place for such
error (at least for a unix port): povms.cpp, circa line 883.

It's in POVMS_Send.

Default timeout is 10 s, but in case of _DEBUG defined, vfe/vfeconf.h
define it to 100 s;

As far as I can see, the timeout is a POVMS property ('TOUT') but is not
settable per ini file.
So, you get stuck 10s (of wall time) and the POVMS system get no
progress on its messages...

What is at the line 39 (and around) of
"C:\$user\pfa_demo\gini\subsurf_mh_f11j.pov" ?

Is the file included on a network drive ? (auto-umount ? any
screen/power saver ? (turn disk off after xx minutes of inactivity ? no
mouse movement-->inactive... ))


Post a reply to this message

From: gregjohn
Subject: Re: Operation timed out? (Win3.7 RC3
Date: 14 Feb 2011 16:55:00
Message: <web.4d59a49ac336e2ac498498110@news.povray.org>
Le_Forgeron <jgr### [at] freefr> wrote:
>
> What is at the line 39 (and around) of
> "C:\$user\pfa_demo\gini\subsurf_mh_f11j.pov" ?
>
> Is the file included on a network drive ? (auto-umount ? any
> screen/power saver ? (turn disk off after xx minutes of inactivity ? no
> mouse movement-->inactive... ))


Line 39 is:

#include"transforms.inc"

The file was on the HDD, in the same directory. There wasn't anything different
for this frame than any others.  If it matters, I've done lots of long term and
overnight renders with this computer and never run into this error before. The
differences are RC3 (I am a latecomer to 3.7, having used MegaPov until just
recently), and that this project had each frame much longer-rendering than most
of those I'd done in the past.

thanks.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.