  | 
  | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
Hi,
   I tried Linux POV 3.7.0-beta14 with some bigger production scene and 
it failed after renderging was complete with this error:
<snip>
Render Time:
   Photon Time:      No photons
   Radiosity Time:   No radiosity
   Trace Time:       0 hours  5 minutes 18 seconds (318.957 seconds)
               using 2 thread(s) with 0.-02 CPU-seconds total
terminate called after throwing an instance of 'pov_base::Exception'
   what():  Unknown internal error!
make: *** [0final01.ppm] Killed
make: *** Deleting file `0final01.ppm'
Unfortunately, I cannot post the scene to a public forum :(. Has anybody 
some idea, how to determine the problem more accurate? (I'll try to 
switch off some parts of the scene, but it will take some time and may 
not lead to any good result, some more detailed error description from 
POV may be useful.)
Best regards
Vaclav
 Post a reply to this message 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
> terminate called after throwing an instance of 'pov_base::Exception'
>   what():  Unknown internal error!
	This is unfortunately a problem we discovered when preparing the Linux beta.
It does happen with some specific scenes (for instance advanced/abyss.pov) but
not others.  While usually reproducible, this problem manifests in different ways
depending on which Linux environment is in use.  For instance, you might also
observe a delay or approx. 20-30 seconds between the display of render stats
and the internal error, or not.  Is it the case for you?  Note that in principle
the output image is produced normally.
	Could you please check whether you get this problem with abyss.pov as well
-- or any other scene in the distribution for that matter -- and if you do observe
some delay before the error pops up?  Thanks!
	- NC
 
 Post a reply to this message 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
> It does happen with some specific scenes (for instance 
> advanced/abyss.pov) but not others.
	FYI, these are the demo scenes in the beta distribution for which
I get the problem you describe:
advanced/abyss.pov
advanced/balcony/balcony.pov
advanced/wallstucco.pov
incdemo/func_gradient.pov
language/splinefunction.pov
textures/finishes/var_refl.pov
	- NC
 
 Post a reply to this message 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
Yes, it is my case, I noticed long delay when ending some scenes.
And yes, I got this problem with the scene abyss.pov. I observed delay 
with this scene before it crashed with error. Rendered image was saved 
correctly, but this behavior is a bit annoying, because I use make for 
rendering more scenes and make deletes resulting file when the program 
returns error status :(
VC
>     This is unfortunately a problem we discovered when preparing the 
> Linux beta.
> It does happen with some specific scenes (for instance 
> advanced/abyss.pov) but
> not others.  While usually reproducible, this problem manifests in 
> different ways
> depending on which Linux environment is in use.  For instance, you might 
> also
> observe a delay or approx. 20-30 seconds between the display of render 
> stats
> and the internal error, or not.  Is it the case for you?  Note that in 
> principle
> the output image is produced normally.
> 
>     Could you please check whether you get this problem with abyss.pov 
> as well
> -- or any other scene in the distribution for that matter -- and if you 
> do observe
> some delay before the error pops up?  Thanks!
> 
>     - NC
 
 Post a reply to this message 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
I also tried to render this scene with very small resolution (6x2 
pixels) and use strace, the result is attached to this message. Don't 
know, if it helps, but it was easy to do ;-))
VC
 
 Post a reply to this message 
 
Attachments: 
Download 'us-ascii' (30 KB)
 
  
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
Hi,
This issue is fixed now, thanks for the report.
-- Chris
 
 Post a reply to this message 
 | 
  | 
 |   | 
 |   | 
 | 
  | 
 | 
  | 
 |   |