POV-Ray : Newsgroups : povray.beta-test : RC4 parse hanging on Pentium G620 : RC4 parse hanging on Pentium G620 Server Time
21 May 2024 05:16:27 EDT (-0400)
  RC4 parse hanging on Pentium G620  
From: harry
Date: 9 Mar 2012 12:35:05
Message: <web.4f5a3ee89e1ca2f9cc84ad830@news.povray.org>
I'm seeing a strange behavior on 3.7.0 RC4 on linux, with included sample
scenes.

First, the particulars:

Slackware 13.37, stock 2.6.37.6 kernel, Slackware default "everything" install
RC4 compiled with Slackware stock gcc 4.52
configure script run with no options except the usual "COMPILED_BY"
Dell R210 hardware, Pentium G620 2.6ghz

What's happening is povray looks to be hanging in the parsing stage.  I tried to
render the "box.pov" file that comes with the distribution.
(/usr/local/share/povray-3.7/scenes/objects/box.pov) and it hangs with the last
of the output like so:


Parser Options
  Input file: box.pov
  Remove bounds........On
  Split unions.........Off
  Library paths:
    /usr/local/share/povray-3.7
    /usr/local/share/povray-3.7/ini
    /usr/local/share/povray-3.7/include
  Clock value:    0.000  (Animation off)
Image Output Options
  Image resolution.....1600 by 1200 (rows 1 to 1200, columns 1 to 1600).
  Output file..........box.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
==== [Parsing...]=======================

Parsing never completes.  Povray seems to be using a single thread, and seems to
allocate memory for the parse and then stop so it doesn't look like some kind of
leak.  It consumes 100% of CPU on the one core as long as I let it run but
either never finishes the parse or never starts the actual render.  Povray
doesn't respond to an abort signal (ctl-c) and has to be killed with signal 9.

Does this sound like a user error or should I file a bug report?  I have done
the same install of the OS and RC4 on different hardware and had no problems but
I'm not sure if I need to pass some configure option for the G620 processor.

Thanks!
harry


Post a reply to this message

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