I get this error message:
"Parse Error: bad allocation  Render failed"
- after the code below has been running for about 3 seconds.

// ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7

#version 3.7;

#while (true)
  #local Fn = function { transform { translate <0, 0, 0> } }
  #undef Fn
#end // while

// ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7

I'm using POV-Ray for Windows - Version 3.7.0.RC3.msvc9-sse2.win32
The operating system is Windows XP.

With the code above, the error messages has so far appeared every time
right after 3318K tokens have been parsed. But with other versions of
my code, the error message does not always show up. (Sometimes the
render finishes and sometimes the parsing stops at different "times".)

See below for the contents of the output pane.

Can anyone else see this problem ?


Tor Olav
http://subcube.com

----------------------------------------------------------------------------
Preset INI file is 'C:\Documents and Settings\tok\Mine
dokumenter\POV-Ray\v3.7\ini\quickres.ini', section is '[800x600, No AA]'.
Preset source file is 'E:\POV-Ray filer\BadAllocationBug_08.pov'.
Rendering with 2 threads.
Parser Options
  Input file: E:\POV-Ray filer\BadAllocationBug_08.pov
  Remove bounds........On
  Split unions.........Off
  Library paths:
    C:\Documents and Settings\tok\Mine dokumenter\POV-Ray\v3.7\include
    C:\WINDOWS\Fonts
  Clock value:    0.000  (Animation off)
Image Output Options
  Image resolution.....800 by 600 (rows 1 to 600, columns 1 to 800).
  Output file..........E:\POV-Ray filer\BadAllocationBug_08.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

-
"E:\POV-Ray filer\BadAllocationBug_08.pov" line 6: Parse Error: bad allocation
Render failed
-
CPU time used: kernel 0.41 seconds, user 2.75 seconds, total 3.16 seconds.
Elapsed time 3.38 seconds.
----------------------------------------------------------------------------

Post a reply to this message

On 04/11/2011 09:41 PM, Tor Olav Kristensen wrote:
>
> I get this error message:
> "Parse Error: bad allocation  Render failed"
> - after the code below has been running for about 3 seconds.
>
> // ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7
>
> #version 3.7;
>
> #while (true)
>    #local Fn = function { transform { translate<0, 0, 0>  } }
>    #undef Fn
> #end // while

where does the conditional get set to false ... don't see that here (or 
any other bail-out mechanism) ... runaway loop?

>
> // ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7
>
> I'm using POV-Ray for Windows - Version 3.7.0.RC3.msvc9-sse2.win32
> The operating system is Windows XP.
>
> With the code above, the error messages has so far appeared every time
> right after 3318K tokens have been parsed. But with other versions of
> my code, the error message does not always show up. (Sometimes the
> render finishes and sometimes the parsing stops at different "times".)
>
> See below for the contents of the output pane.
>
> Can anyone else see this problem ?
>
>
> Tor Olav
> http://subcube.com
>
> ----------------------------------------------------------------------------
> Preset INI file is 'C:\Documents and Settings\tok\Mine
> dokumenter\POV-Ray\v3.7\ini\quickres.ini', section is '[800x600, No AA]'.
> Preset source file is 'E:\POV-Ray filer\BadAllocationBug_08.pov'.
> Rendering with 2 threads.
> Parser Options
>    Input file: E:\POV-Ray filer\BadAllocationBug_08.pov
>    Remove bounds........On
>    Split unions.........Off
>    Library paths:
>      C:\Documents and Settings\tok\Mine dokumenter\POV-Ray\v3.7\include
>      C:\WINDOWS\Fonts
>    Clock value:    0.000  (Animation off)
> Image Output Options
>    Image resolution.....800 by 600 (rows 1 to 600, columns 1 to 800).
>    Output file..........E:\POV-Ray filer\BadAllocationBug_08.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
>
> -
> "E:\POV-Ray filer\BadAllocationBug_08.pov" line 6: Parse Error: bad allocation
> Render failed
> -
> CPU time used: kernel 0.41 seconds, user 2.75 seconds, total 3.16 seconds.
> Elapsed time 3.38 seconds.
> ----------------------------------------------------------------------------
>
>
>
>

Post a reply to this message

Jim Holsenback <jho### [at] povrayorg> wrote:
> On 04/11/2011 09:41 PM, Tor Olav Kristensen wrote:
> >
> > I get this error message:
> > "Parse Error: bad allocation  Render failed"
> > - after the code below has been running for about 3 seconds.
> >
> > // ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7
> >
> > #version 3.7;
> >
> > #while (true)
> >    #local Fn = function { transform { translate <0, 0, 0> } }
> >    #undef Fn
> > #end // while
>
> where does the conditional get set to false ... don't see that here (or
> any other bail-out mechanism) ... runaway loop?

This is just a as-simple-as-possible scene that will give this error message.
Other versions of my code has a simple counting loops and it still triggers this
error message.

Also see my other comments below.


> > // ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7
> >
> > I'm using POV-Ray for Windows - Version 3.7.0.RC3.msvc9-sse2.win32
> > The operating system is Windows XP.
> >
> > With the code above, the error messages has so far appeared every time
> > right after 3318K tokens have been parsed. But with other versions of
> > my code, the error message does not always show up. (Sometimes the
> > render finishes and sometimes the parsing stops at different "times".)
> >
> > See below for the contents of the output pane.
> >
> > Can anyone else see this problem ?
> >
> >
> > Tor Olav
> > http://subcube.com
> >
> > ----------------------------------------------------------------------------
> > Preset INI file is 'C:\Documents and Settings\tok\Mine
> > dokumenter\POV-Ray\v3.7\ini\quickres.ini', section is '[800x600, No AA]'.
> > Preset source file is 'E:\POV-Ray filer\BadAllocationBug_08.pov'.
> > Rendering with 2 threads.
> > Parser Options
> >    Input file: E:\POV-Ray filer\BadAllocationBug_08.pov
> >    Remove bounds........On
> >    Split unions.........Off
> >    Library paths:
> >      C:\Documents and Settings\tok\Mine dokumenter\POV-Ray\v3.7\include
> >      C:\WINDOWS\Fonts
> >    Clock value:    0.000  (Animation off)
> > Image Output Options
> >    Image resolution.....800 by 600 (rows 1 to 600, columns 1 to 800).
> >    Output file..........E:\POV-Ray filer\BadAllocationBug_08.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
> >
> > -
> > "E:\POV-Ray filer\BadAllocationBug_08.pov" line 6: Parse Error: bad allocation
> > Render failed
> > -
> > CPU time used: kernel 0.41 seconds, user 2.75 seconds, total 3.16 seconds.
> > Elapsed time 3.38 seconds.
> > ----------------------------------------------------------------------------

--
Tor Olav
http://subcube.com

Post a reply to this message

"Tor Olav Kristensen" <tor### [at] TOBEREMOVEDgmailcom> wrote:
....
> I'm using POV-Ray for Windows - Version 3.7.0.RC3.msvc9-sse2.win32
> The operating system is Windows XP.
....
> Can anyone else see this problem ?
....
Yes, about 7sec every time

Windows Vista sp2
POV-Ray 3.7.0.RC3.msvc9.win64
No, let run 5 min then manualy stopped,tested 6 times.

Windows 7
POV-Ray 3.7.0.RC3.msvc9.win64
No, let run 7 min.

Stephen S

Post a reply to this message

On 12/04/2011 1:41 AM, Tor Olav Kristensen wrote:
> I get this error message:
> "Parse Error: bad allocation  Render failed"
> - after the code below has been running for about 3 seconds.
>
> // ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7
>
> #version 3.7;
>
> #while (true)
>    #local Fn = function { transform { translate<0, 0, 0>  } }
>    #undef Fn
> #end // while
>
> // ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7
>
> I'm using POV-Ray for Windows - Version 3.7.0.RC3.msvc9-sse2.win32
> The operating system is Windows XP.
>
> With the code above, the error messages has so far appeared every time
> right after 3318K tokens have been parsed. But with other versions of
> my code, the error message does not always show up. (Sometimes the
> render finishes and sometimes the parsing stops at different "times".)

Using POV-Ray for Windows - Version 3.7.0.RC3.msvc9-sse2.win32 OS Win 7
The code ran for > 5 minutes, > 844000K tokens without failing.
I ran it several times.

-- 
Regards
     Stephen

Post a reply to this message

Tor Olav Kristensen wrote:

> Can anyone else see this problem ?

Don't see it here with 64-bit version on Windows 7.

However, memory use increases by 1.2 GB during parsing
before going into into saturation. So whether the bad alloc
occurs may simply be due to available memory.

Post a reply to this message

Jim Holsenback <jho### [at] povrayorg> wrote:
> On 04/11/2011 09:41 PM, Tor Olav Kristensen wrote:
> >
> > I get this error message:
> > "Parse Error: bad allocation  Render failed"
> > - after the code below has been running for about 3 seconds.
> >
> > // ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7
> >
> > #version 3.7;
> >
> > #while (true)
> >    #local Fn = function { transform { translate<0, 0, 0>  } }
> >    #undef Fn
> > #end // while

> where does the conditional get set to false ... don't see that here (or 
> any other bail-out mechanism) ... runaway loop?

  I don't think that's the point. The above code doesn't look like it should
give any kind of error. Instead, it should just run indefinitely.

-- 
                                                          - Warp

Post a reply to this message

On 04/12/2011 01:54 PM, Warp wrote:
> Jim Holsenback<jho### [at] povrayorg>  wrote:
>> On 04/11/2011 09:41 PM, Tor Olav Kristensen wrote:
>>>
>>> I get this error message:
>>> "Parse Error: bad allocation  Render failed"
>>> - after the code below has been running for about 3 seconds.
>>>
>>> // ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7
>>>
>>> #version 3.7;
>>>
>>> #while (true)
>>>     #local Fn = function { transform { translate<0, 0, 0>   } }
>>>     #undef Fn
>>> #end // while
>
>> where does the conditional get set to false ... don't see that here (or
>> any other bail-out mechanism) ... runaway loop?
>
>    I don't think that's the point. The above code doesn't look like it should
> give any kind of error. Instead, it should just run indefinitely.
>
LOL ... on a more serious note I do believe that I've been seeing this 
manifest itself slightly different on 32bit linux

sometimes my scene would parse the just as it pops up the preview window 
it freezes, and requires a kill -9 to get it to let go. After the kill 
-9 and with no scene file changes and resubmit the render ... it worked 
just fine. One time I let it keep going because I'd thought I was being 
impatient ... next morning it was still hung and fuxtex or mutex (I 
forget) was the process table hog ... that's boost trying to allocate 
correct?

IIRC ... this started about the time we didn't have to specify the boost 
configure option ... maybe just a co-incidence.

this last cycle (RC3-RC4) there were one or two problems that couldn't 
be duplicated on 64bit systems ... that is ... they were problems that 
in one way or another couldn't be confirmed by the developers until I 
learned how to use gdb and supplied more useful information

maybe this is another one of those 32 -vs- 64bit scoundrels ... does the 
win32 bit problem that started this thread offer to send a mini dump? on 
linux hard fails like this usually has a segmentation fault, but like I 
mentioned mine never did (seg fault) it just hung and continued to 
consume cpu cycles

Post a reply to this message

Jim Holsenback <jho### [at] povrayorg> wrote:
> sometimes my scene would parse the just as it pops up the preview window 
> it freezes, and requires a kill -9 to get it to let go. After the kill 
> -9 and with no scene file changes and resubmit the render ... it worked 
> just fine. One time I let it keep going because I'd thought I was being 
> impatient ... next morning it was still hung and fuxtex or mutex (I 
> forget) was the process table hog ... that's boost trying to allocate 
> correct?

  That sounds to me like a livelock caused by a race condition.

-- 
                                                          - Warp

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote:
> Jim Holsenback <jho### [at] povrayorg> wrote:
> > On 04/11/2011 09:41 PM, Tor Olav Kristensen wrote:
> > >
> > > I get this error message:
> > > "Parse Error: bad allocation  Render failed"
> > > - after the code below has been running for about 3 seconds.
> > >
> > > // ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7
> > >
> > > #version 3.7;
> > >
> > > #while (true)
> > >    #local Fn = function { transform { translate<0, 0, 0>  } }
> > >    #undef Fn
> > > #end // while
>
> > where does the conditional get set to false ... don't see that here (or
> > any other bail-out mechanism) ... runaway loop?
>
>   I don't think that's the point. The above code doesn't look like it should
> give any kind of error. Instead, it should just run indefinitely.

Yes, that was my intention.

I have been running the same code (without the version directive) on POV-Ray
version 3.6.2.msvc9-sse2 for over 7 hours on another Windows XP SP3 PC.

67.801.367.203 tokens have been parsed so far without any problems.

--
Tor Olav
http://subcube.com

Post a reply to this message