When trying to run a render that uses over 3Gb memory I get this error

  0:01:18 Creating vista bufferPOVMS_ASSERT failed in povms.cpp line 2183:
POVMSObject_Set failed, out of memory
POVMS_ASSERT failed in povms.cpp line 2849: POVMSAttr_Set failed, out of
memory
POVMS_ASSERT failed in povms.cpp line 2183: POVMSObject_Set failed, out of
memory
POVMS_ASSERT failed in povms.cpp line 2183: POVMSObject_Set failed, out of
memory
POVMS_ASSERT failed in povms.cpp line 2183: POVMSObject_Set failed, out of
memory
Segmentation fault

Keeping it below 3Gb (by reducing the number of lights) it works fine.

Just wondering if I should keep that 3Gb limit in mind or if there is
something else going wrong.

Running:
Athlon 64x2 3800+
4 Gb mem internal (6Gb swap) (so available mem should not be a problem)
Suse 10 with Linux athlon64 2.6.13-15-bigsmp kernel
Self compiled Povray 3.6.1
-- 
Ger

Post a reply to this message

Ger wrote:
> [...]
> 
> Just wondering if I should keep that 3Gb limit in mind or if there is
> something else going wrong.
> 
> Running:
> Athlon 64x2 3800+
> 4 Gb mem internal (6Gb swap) (so available mem should not be a problem)
> Suse 10 with Linux athlon64 2.6.13-15-bigsmp kernel
> Self compiled Povray 3.6.1

I suggest you check your system configuration and compiler settings. 
POV-Ray has no internal limitations concerning memory use.

Christoph

-- 
POV-Ray tutorials, include files, Landscape of the week:
http://www.imagico.de/ (Last updated 31 Oct. 2005)
MegaPOV with mechanics simulation: http://megapov.inetart.net/

Post a reply to this message

Christoph Hormann wrote:

> 
> I suggest you check your system configuration and compiler settings.
> POV-Ray has no internal limitations concerning memory use.
> 
> Christoph
> 

Okay, thanks Christoph. I'm just trying to eliminate possible causes.
Next step is reinstall the system and try again :)
-- 
Ger

Post a reply to this message

Ger wrote:

> Next step is reinstall the system and try again :)

Ah, yes.  The Microsoft solution.

Regards,
John
(who couldn't resist)

Post a reply to this message

John VanSickle wrote:

> Ger wrote:
> 
>> Next step is reinstall the system and try again :)
> 
> Ah, yes.  The Microsoft solution.
> 
> Regards,
> John
> (who couldn't resist)

Who's Microsoft?

-- 
Ger

Who couldn't resist either

Post a reply to this message

John VanSickle wrote:
> 
>> Next step is reinstall the system and try again :)
> 
> Ah, yes.  The Microsoft solution.

But that only works on Microsoft system - elsewhere performing the same 
installation once more will not lead you any further...

Christoph

-- 
POV-Ray tutorials, include files, Landscape of the week:
http://www.imagico.de/ (Last updated 31 Oct. 2005)
MegaPOV with mechanics simulation: http://megapov.inetart.net/

Post a reply to this message

Christoph Hormann wrote:

> John VanSickle wrote:
>> 
>>> Next step is reinstall the system and try again :)
>> 
>> Ah, yes.  The Microsoft solution.
> 
> But that only works on Microsoft system - elsewhere performing the same
> installation once more will not lead you any further...
> 
> Christoph
> 
The most likely reason for the troubles I'm seeing these last 2 weeks is the
fact that I increased memory from 2 to 4 Gb, switched out the video card
and added an Adaptec UW320 controller.Because of the memory I had to switch
kernel. It's in this kernel switching together with the new drivers that
something got screwy.
-- 
Ger

Post a reply to this message

Ger wrote:
> Christoph Hormann wrote:
> 
>> John VanSickle wrote:
>>>> Next step is reinstall the system and try again :)
>>> Ah, yes.  The Microsoft solution.
>> But that only works on Microsoft system - elsewhere performing the same
>> installation once more will not lead you any further...
>>
>> Christoph
>>
> The most likely reason for the troubles I'm seeing these last 2 weeks is the
> fact that I increased memory from 2 to 4 Gb, switched out the video card
> and added an Adaptec UW320 controller.Because of the memory I had to switch
> kernel. It's in this kernel switching together with the new drivers that
> something got screwy.

Have you checked ulimit to see what your stack size and allowed virtual
memory are? 'ulimit -a' at the console should give you the values that
the system is currently set to allow. I'm not sure what Suse would set
their defaults at, but I think they would pick more conservative defaults.
The other option would be the memory settings in the kernel, but that
still shouldn't require a reinstall.

--
I want Linux to replace Windows, but I don't think this is what I had in
mind.

Post a reply to this message

Sabrina Kilian wrote:

> 
> Have you checked ulimit to see what your stack size and allowed virtual
> memory are? 'ulimit -a' at the console should give you the values that
> the system is currently set to allow. I'm not sure what Suse would set
> their defaults at, but I think they would pick more conservative defaults.
> The other option would be the memory settings in the kernel, but that
> still shouldn't require a reinstall.
> 

Hi, no, I have not checked those values, but after a re-install it all works
out nicely. It must have been a kernel problem because now I can run
renders as large as 10Gb* without too much trouble.

And for your info
core file size        (blocks, -c) 0
data seg size         (kbytes, -d) unlimited
file size             (blocks, -f) unlimited
max locked memory     (kbytes, -l) 32
max memory size       (kbytes, -m) unlimited
open files                    (-n) 1024
pipe size          (512 bytes, -p) 8
stack size            (kbytes, -s) unlimited
cpu time             (seconds, -t) unlimited
max user processes            (-u) 40960
virtual memory        (kbytes, -v) unlimited


> --
> I want Linux to replace Windows, but I don't think this is what I had in
> mind.

-- 
Ger

[*] With a lot of random included crap just to make the render bigger.

Post a reply to this message

Ger wrote:
> When trying to run a render that uses over 3Gb memory I get this error
> 

...


> Keeping it below 3Gb (by reducing the number of lights) it works fine.
> 
> Just wondering if I should keep that 3Gb limit in mind or if there is
> something else going wrong.
> 
> Running:
> Athlon 64x2 3800+
> 4 Gb mem internal (6Gb swap) (so available mem should not be a problem)
> Suse 10 with Linux athlon64 2.6.13-15-bigsmp kernel
> Self compiled Povray 3.6.1

It looks like you know what you are doing, but here are some things I 
have run across regarding memory - based on 32 bit systems.

A single application (thread) is limited to using 2GB or 3GB depending 
on your OS and settings within the OS.  I have found that typically in 
Windows the limit is 2GB and Linux is 3GB (tho these can be affected by 
OS settings).  I have run into these ceilings myself running various 
applications.  I have found no way of allowing for more memory usage in 
a 32bit system.  I set up 16GB swap once only to have the application 
crash at 3GB.

Also, the OS might be capable of using much more than 2GB (or 3GB), but 
it must be in the form of separate applications (or threads).  It might 
be entirely possible to run (3) 2GB applications - tho I have not tried 
or tested this myself.  Others here with more knowledge can set me straight.

I remember that these is a configuration within Linux that allows it to 
use different memory mapping to allow for large memory usage.  If I 
remember correctly, it was a kernel option and required the kernel to be 
recompiled.

If your system is 64 bit, it could be that something is still limiting 
it to using 32 bit memory addressing.

Now, my experience is only with a 32 bit system.  I understand that 64 
bit systems have much different limitations, but I have no experience 
with them.  I hope that this sheds a bit of light for you.




LAter... Tom

Post a reply to this message